Because there is no interface for writing GPU drivers on Apple Silicon macOS. See my post above.
There are no GPU driver tools for Apple Silicon on Linux either, and yet such drivers have been created. So maybe someone exceptionally talented would be able to figure something out.
By 'interface', I think
@leman meant a way to actually 'connect' the driver to the OS.
Linux certainly has the ability to have lots of video drivers... and more importantly, it's open source, you have the source code in front of you. All the Apple Silicon on Linux folks had to do is reverse engineer the M1 graphics, write a Linux driver for it, add it to their kernel tree, and, once it's ready, send it upstream to Mr. Torvalds & co. to be added into the main kernel tree. Nothing controversial here - the frameworks already exist in the Linux kernel to support Intel, AMD, NVIDIA and lots of others - see
https://en.wikipedia.org/wiki/Direct_Rendering_Manager and scroll down to the supported hardware section.
That is a lot easier than writing a driver for a (closed-source) OS that wasn't designed to have such drivers written for it.
Somewhere in between, you have an OS like (x86) Windows, which is closed source
but designed to accommodate a lot of drivers for a lot of different hardware types.
It's worth noting, the entire concept of drivers in the Windows sense is somewhat unusual outside the 'IBM-compatible' x86 world. The more common model would have been the CP/M or Android model where the hardware maker licences the OS, modifies the OS source code to support the hardware they want to include, and then ships their product with their build of the OS that they are then responsible for supporting (or not supporting, in the case of many Android OEMs). The Apple model has been somewhat like that too - for some hardware types, the OS supports what Apple feels like it's going to support, and then doesn't have any way to add drivers for other models; for other hardware types, e.g. printers, the OS will allow third-party drivers.