Kernel modules need to be written for the operating system, so this means there would need to be a userbase present on Linux/macOS to justify writing such a driver (writing kext for macOS is even more difficult as Apple has more or less banned them).
You don't want these types of anti-cheat. I would encourage anyone looking into games that use kernel modules for anti-cheat to avoid them.
Unfortunately user-mode anti-cheat has been defeated time and time again.
There's also a second category of anti-cheat (kernel-level), which will never work on Linux, as @p_ing elaborated. I second their opinion that you shouldn't run games which use these, even on Windows. The Crowdstrike incident has shown us how dangerous such programs can be (causing BSODs and instability). Kernel-level anti-cheat programs are even more dangerous, since they monitor everything on your PC, actively sabotages any inspection tools, and protects itself from being uninstalled - which is behaviour very akin to malware/rootkits. You should _never_ install such programs on your PC. Once again, the solution here is to vote with your wallet and boycott games and studios which use such solutions.
An open source operating system could be used to block or circumvent the control check points of said spyware. So installing it on your Linux workstation may not provide enough guarantees.
But... the unasked question, but important one is: why install one on _your_ computer? If someone (school, org, whatever) needs you to pass a test, they can provide the whole package if they want to exert control over the whole context of the test.
But submitting in advance to their own requirement (it's not _your_ requirement), by compromising your own computer?
This may as well be a hidden purpose test, where refusing to install said software is the "good" answer. And if the employer doesn't accept/understand that, that's... problematic for them on a whole other level.
You could make one that works for Ubuntu.
Anti-cheat often tries to detect suspicious modules, for example. On Linux, that suspicious module could be a buggy or obscure driver for some obscure piece of hardware. On Windows, at least it's signed by Microsoft saying "this is a real driver for an obscure piece of hardware".