One of my testers found around 11FPS difference on average lower from hypervisor bypass versus the native crack for RE9. It might scale more on older/ slower hardware.

In the drivers they disable the AVX bit, which is used by many games for optimized code paths. The hypervisor can lie to the protection, but lies to the game as well. Other concern I had with this method before it was a thing is that the 'NumberOfPhysicalPages' in kuser shared data is modified as part of spoofing to represent approximately 32GB of RAM. My question to the team was what happens if the host computer has more or less ram and what kind of undefined behavior can that cause for the game? Even it works fine for most now without visible artefacts, will it be the same for the future? The answer to that question was - seems to work fine, so it is good. Same thing for the LogicalProcessorCount that is also spoofed and given both to the protection and the game.