> TL;DR Yes we run a driver at system startup, it doesn't scan anything (unless the game is running), it's designed to take up as few system resources as possible and it doesn't communicate to our servers. You can remove it at anytime.
As a person who actually plays the game on a M1 Pro MacBook running in x86 emulation, which is not supported by kernel mode drivers, I can tell you with absolute certainty (unless of course Riot has found an exploit that allows installation of unsigned system drivers), that my computer has no non-apple drivers installed.
That's the anti-cheat which only Valorant uses
Mate you are chastising him for not reading the article and you are contradicted by the first paragraph.
Code running in the kernel context is different than code running in the user context. Another process can modify user context, whereas it is expected that code running in the kernel context is "much harder".
A dedicated attacker could write kernel code which does the modifications, however this raises the bar and the anti cheat software could the game from running if it detects any unsigned drivers.
All this does is raise the bar to where the game is run into virtualization where the host OS can inspect the guests memory and infer details that way. The cat and mouse game goes on forever, the trick is to make it just hard enough so that the average person who wants to cheat will not not have the time, patience or financial incentive to do so.