Well I personally can’t stand the idea of Google GSF
I can actually understand that, and I had the same thought when I started using GrapheneOS. But microG is just an open source layer that requires proprietary Google blobs in the background, which sits between the proprietary Google Play services library in proprietary apps and proprietary Google network services. You gain almost nothing from using it, while simultaneously increasing attack surface, due to microG's requirement for root privileges.
MicroG also is very flexible on how it works. It is broken down into lots of different services.
Can you really control which parts of microG are active? This suggests the opposite: https://discuss.grapheneos.org/d/4290-sandboxed-microg/18
From the thread:
Signal is a perfect example where the app works fine without Google Play including with push but will not work correctly in a setup you proposed in the other thread of using it with FCM disabled. That breaks the app and it won't get calls or push notifications anymore, unlike using it in a profile without Google Play
(Yes, I know that the GrapheneOS Forum might be a biased source when talking about this topic, but I currently don't have any way of testing this out with microG. If you don't believe what the Graphene dev is saying in the forum thread, you can try it out for yourself)
The only part of microG that I would really consider using is UnifiedNLP, together with a privacy-friendly network location service. There was actually a discussion about including UnifiedNLP in GrapheneOS, but I think there were some licensing issues. (GrapheneOS can't use GPLv3 code. GPLv2, MIT and Apache are fine though). But Graphene's SUPL & PSDS-based approach for obtaining location information currently works well enough, and they might integrate an open, privacy-friendly NLP like beaconDB in the future.
I looked at some other ROMs, and I could hardly find any feature that's worth including in the comparison table. Specifically, I looked at the features page of CalyxOS: https://calyxos.org/features/
That's an AOSP feature I guess
is not an OS feature, as it's simply implemented in the Dialer, which can freely be changed by the user. Putting this in an OS comparison table wouldn't make any sense, as it isn't an OS feature, but rather a feature of an individual app.
These two points also use the original GrapheneOS code and they aren't unique to Calyx. Sure, these could be included, but it wouldn't give Calyx any advantage.
(Sorry for the bad formatting btw, but it should still be understandable)
The comparison table is absolutely not biased. It is clear that it's focused on security, and it factually compares the security features of different ROMs. Feel free to create your own objective, factual comparison table that focuses on other aspects.