GrapheneOS moderator here, I thought I’d chime in with some thoughts.
I agree that the “simplified” table in this guide leads to a lot of incomplete conclusions. I generally already consider a table to be a bad way to convey information about complex topics with a lot of nuance, but Eylenburg’s table at the very least includes more along with tooltips for descriptions and explanations, links etc.
In my opinion, that section of the page should just link to Eylenburg’s existing table rather than trying to simplify it which can lead to more confusion than just referring to that.
This isn’t entirely true, DivestOS has unprivileged microG.
This is true, however, implementing microG in this way requires OS work which GrapheneOS doesn’t include, so microG doesn’t make sense for GrapheneOS users. Someone can install the microG app on an OS as a regular sandboxed app, but there’s a lot it won’t do (most functionality, really) without special integration to some degree, so for a GrapheneOS user, there doesn’t really seem to be a case in which it would make sense to opt for that.
I also don’t think there is enough warning given to installing the optional Google Play Services, it’s pretty invasive to install Google Play Services on your device even if it is Sandboxed. You are sending quite a lot of info about your device to Google, such as the apps you have installed, IP address, device type, etc etc.
It is not clear how sandboxed Google Play is more invasive than installing other apps that run Google Play code and libraries, given that they’re both constrained in the same app sandbox. Apps which are going to use Google Play contain Google Play libraries which does have the same access as sandboxed apps which includes allowing it to see what other apps you have installed, your IP address, etc.
The entire approach of sandboxed Google Play is that it’s not giving things more access over any other app.
I do agree that the very simplistic way it’s portrayed in the table doesn’t help people understand the difference between the various options but it is important to mention that there is a pretty significant difference. If I am not mistaken, AOSP is taking steps upstream that will hopefully bring Android closer to what GrapheneOS does, which is good to see.