

Not whatsoever.
Practically any mining software would allow you to change a pool whenever you felt like it, and making a script that just goes “oh, x.x.x.x isn’t responding anymore, I should point my hashrate to y.y.y.y now” is… not hard, to say the least.
But that’s the thing: GrapheneOS doesn’t exist to “escape google,” it exists to give people privacy.
If it were designed to escape google, they wouldn’t create a re-implementation of Google Play Services that you can optionally install for apps that need it and regularly maintain it with every OS update.
GrapheneOS doesn’t remove Google services because “Google specifically bad,” they remove Google services because they spy on you without consent, and GrapheneOS is meant to prevent spying.
Hell, if any ROM wanted to get away from Google, basing itself on Android, the thing developed by Google would then be the problem, and they would be better off trying to make an independent Linux distro.
It fundamentally makes sense for GrapheneOS to work on Google hardware first, because Google controls not just the hardware supply chain of the phones, but also the software supply chain. (AOSP)
Supporting, say, Samsung phones, would then mean not just, to a degree, relying on Google via AOSP, but also Samsung’s hardware. Android-based ROMs can’t really benefit from trying to get away from a particular company, because it’s either Google, or Google + Phone Manufacturer that they then have to deal with. (not to mention the fact that Pixels run the best with stock android and are simply the most feasible device for a small development team to support with the lowest possible costs)