

There needs to be a give and take
If GrapheneOS can’t handle the maintenance burden, there is nothing to negotiate.
Presumably, maintaining software for a niche phone requires effort similar in magnitude to a larger, mainstream phone. Why, then, would a solely privacy-oriented org choose to cater to a smaller audience?

GrapheneOS is an open-source fork of AOSP. Anyone could fork it again and provide kernel modules/drivers for their hardware.
To my knowledge, GrapheneOS is not standards-based. They take one operating system, and tweak it. I don’t know if there are relevant standards to contribute to, or even standards bodies to approve them.