The ARM server ecosystem has it solved with SBSA, which includes ACPI, UEFI, etc as part of the standard.
There are some ARM consumer computers that implement UEFI, etc, though.
The issue is that it's cheaper to just put together bespoke boards and not implement industry standards that are expected on PCs. Vendors don't have to worry about supporting anything other than the hardware and images they ship, so they don't see a reason to make third party OS support viable.
> Is this the reason, why the Android echosystem is so abysmal when it comes to hardware driver support?
Theoretically, Android should have all of the same drivers as Linux, along with Android-specific drivers that are abstracted over stable driver interface instead of the unstable Linux interface.
What usually happens is the plethora of drivers that vanilla Linux ships with aren't built for, and distributed with, phones/tablets, and the Android drivers only have to support that specific board's hardware. Then, over time, the kernel doesn't get updated so new hardware won't be supported the longer you use the device.
If you're asking why Android devices have poor support for Linux, the OP's answer is the exact reason why.
Is this the reason, why the Android echosystem is so abysmal when it comes to hardware driver support?