I don't login to any google service, but backend magic could be done to correlate identity, yes. Not so different than how browser fingerprinting works.

The secondary apps are known to the owner profile even when the user content is isolated and encrypted, so that is one point of correlation.

If IMEI/SIM is available in local variable space and to apps, then it is another conduit to fingerprinting.

For me, I am willing to make that tradeoff. If you were trying to hide from a nation state (not recommended) you'd probably want physical seperation from true name/anon usage.

Same it true with your desktop, which explains the appeal of Qubes. Just be sure you really need it before attempting to absorb the extremely significant costs of maintaing such a setup. 

 If I cared, I would engage with the #GrapheneOS team in their new discord to hypothesize how fingerprinting might be done and determine how/if #GrapheneOS thwarts potential fingerprinting today. 

 My goal is to raise the cost of tyranny signifantly without pricing myself out of the usage/maintenance cost.

The model I layed forward would sufficiently defend you from IRL cohersion, but not from the security state.

If you are really trying to hide from the security state, God help you. cc @Snowden . 

 Understood, not knocking the strategy, just asking to understand tradeoffs 

 It's a good question, and I should have clarified. This setup makes in-person surveillance prohibitively expensive without sacrificing too much usability, allowing the device to be used as a daily driver. 

 Degoogled phones should be free of Google querying the modem for the IMEI. The towers will still see that though. IMSI is tied to Sim so change it often or  take it out cause it always broadcasts.