Neither microg or grapheneos solves all problems. I don’t think the question here is mainly about google’s tracking components, I think it is instead about system design to avoid leaking data.
That being said, as far as I know accelerometer and compass is still available to apps in an unrestricted manner even in the background, similarly with the speaker through which apps are still allowed to produce sounds that your can’t hear, but tracking systems in the mall or even in smart devices at home listen to it.
The same can really be said about any other sensor with the exception of the mic and the cams because of permissions, but the impact of permissions really get nullified when your smartphone comes from the factory with 3 facebook apps installed, where 2 of them is an unremovable system app with all permissions granted. You still can’t limit whether an app should have access to devices on the LAN when connected to WiFi, which means your phone (through a malicious app) can act as a gateway for tracking data if let’s say you have blocked your smart tv from internet access (either directly, or by just the facebook app scraping all information of all devices on your network, that may also include data in how you use it (screen on time hours), or collected data that was expected accidentally or not).
There are several other points here too that I haven’t mentioned.