Agree that network filtering per se isn't that important a feature to be baked in to GrapheneOS. There's a case to be made for network monitoring (observe what's going on & report to the developer if one spots any anomalies), however; but I digress.
GrapheneOS Most data sharing with third parties is done server side
I'd not say most, but yeah, data brokers do pay a good dime if you can ship clickstream / data out to them, either directly or via your own servers. Cost-wise and tech-wise, not all app developers are equipped to setup a server-side data firehose and so they may opt to bundle in the SDK as-is.
GrapheneOS This still permits everything on the server side if a single domain or IP belonging to the app developers is allowed
True.
I can show you screenshots from my Android, and the number of different services / ASNs some apps hit. It is nice to be able to restrict apps to known ASNs (Meta ASNs for WhatsApp, for example). In the odd chance an app tries to contact a domain / IP it normally wouldn't (WhatsApp loading webpage previews, for instance), it'd be auto-blocked: Just because someone shares a link to a product on Amazon over WhatsApp and WhatsApp decides to auto-preview that link (and now Amazon knows what's up from my IP), I'd rather not get bombarded with ads for similar products on websites that bake in Amazon's ad network.
But you're right, this is akin to blocking telemetry / analytics / etc, while the app may itself forward the more sensitive stuff to its own servers. In that case, I guess, Privacy Policy / EULAs are the only indicators left to gauge the extent of it.
GrapheneOS those companies very actively contact app developers with offers.
Having been subject to some very lucrative offers, I attest to what you're saying.
I wonder if some of these apps minimize data collection if they're on metered networks (ex: Mobile). If so, Android lets a VPN app setup the tunnel so it appears as metered to installed apps.