In a way, it's true that it's none of their business which softwares you use, but it's also their business to make sure the multiplayer experience is fair for the entire userbase.
I guess that's the beauty of games consoles, where the execution of softwares is tightly controlled to minimize piracy and cheaters.
Everything that makes the game fun is defeated by a single cheater.
So people are just going to choose between playing with 0 cheaters or go play a different game.
When games switched from server browsers to matchmaking, they just defaulted to using the anti-cheat system.
Private cheats usually require being vouched in, sometimes with ID scans, sometimes physically shipping you hardware.
I get the sentiment here but we're specifically talking about a mechanism specifically designed to detect other software that is used for cheating.
The alternative is a world where games will only run on machines with SecureBoot, a signed kernel with kernel security on, and only whitelisted signed modules.
There isn't a good solution for how to run games where the clients have to be semi-trusted on a hardware and software stack controlled by the user. If you give me total control over the environment in which a program runs I can make it do and believe anything.
If it is only as good as a real player than it won’t be invincible and will be equivalent to playing with a few AIs in a multiplayer game - which already happens.
Also, I believe the exact mouse movement will not be the same for a human and an aimbot - so not only statistics can be used to ban players
So you have two choices here. You either ban the best players or the aim bots just behave with a success rate close to the best players.
And when I'm talking about statistics here, I'm not referring to the kill/death ratio, but rather all input data received from a cheater.
I recall seeing players hovering in the air and spinning while shooting rockets out at hundreds of rounds a second. There was also a way to modify your files such that you could crash a game just by joining it. The experience was as interesting and fun as it was awful.
These checks have in the past been notoriously buggy, and can interfere with other operations.
This kind of crud is what remote attestation is for, and Microsoft should be responsible for developing it, not every different gaming company competing with each other for kernel access.