Wine does translate kernel calls. Perhaps youre misunderstanding how that is then exposed?

Wine translates windows calls (including system level/kernel level) but exposes/implements in userspace on linux.

It doesn’t only do windows userspace to linux userspace

Its a design decision from the wine team to not build it as a kernel module and to instead implement as an application in userspace

Have a read here https://werat.dev/blog/how-wine-works-101/

If you wanted to support all possible drivers, you would basically need to rewrite the entire kernel. You could make one specific anticheat work by supporting its specific calls, but this will take a lot of work, and will probably be broken with the first ever update.

In the past there were projects that supported specific types of drivers, such as ndiswrapper, but that had a very limited scope.

Here's also an answer to a similar question: https://unix.stackexchange.com/questions/544776/installing-proprietary-windows-drivers-on-linux

WINE loads the executable binary data into the memory, and runs it. The Machine doesn't care if the code was made for Windows or Linux when it runs it

The funny thing here is that Microsoft did a very good job in WSL v1 doing the exact opposite. Unlike Windows apps that run all broken under Wine, running GUI app on WSL worked just fine.

That's more or less what a virtual machine does. And I bet cheating programs do as well.

Not really

It is the difference between kernel space and user space