

Which is why I prefer the MacOS approach better - instead of relying on the developer adding a hypervisor, Apple uses binary signatures for all the relevant system files which are attested via something similar to Secure Boot, plus an Apple-provided API for runtime attestation, to ensure that the system has not been touched since boot. I suspect that Valve’s assistance in making Arch Linux builds reproducible is pointing towards that goal.
I’d settle for that solution anyways, but only as long as users can still mix and match kernels (one for secure boot and games that require anti-cheat, and another for custom hardware)