> building those alternatives is basically impossible
For smart people it is not impossible. Just few years ago, few folks wrote complicated drivers for completely closed hardware, and I'm talking about M1 Macbook.
Google Pixel, on the other hand, was pretty open until very recently. I might be wrong about specifics, but I'm pretty sure that most of software was open, so you could just look at the kernel sources in the readable C to look for anything. You can literally build this kernel and run linux userspace and go from there to any lengths of development. Or you can build alternative systems, looking at driver sources.
I don't understand why mobile systems do not attract OS builders.
My guess would be that it's a continuously moving target. There's no point in spending years working to support some weird integrated wifi adapter+battery controller when by the time you're done the hardware is already obsolete and no longer being manufactured. Repeat that for every device on the phone. The only ones who can keep up with that pace are the manufacturers themselves. It'd be different if there was some kind of standardization that would make the effort worthwhile, though.