The next choice will be dynamically resolving syscall IDs from NTDLL? Surely that has no issues that could possibly happen.