Galaxy S7 user here, on 0.7-2019081029798
The phone does extra stuff with your /e/ account, saving everything on a nextcloud instance, especially for it, so it doesn’t of course use Google one (Except if explicitly asked in that fixed mistake on the calendar app, but i doubt the rest of the “Google configuration” process will work, as it’s setup to synchronise with that nextcloud instance instead.
Again, for the contact app, if you’ve signed up with your /e. account, it will be synchronized on that nextcloud instance. Otherwise it will only stay on the phone.
I don’t use OpenTask aswell, so let’s not care about that.
And well, i think the standard keyboard doesn’t have any privacy problems in itself, even if in the future, using any FOSS alternatives like AnySoftKeyboard would be ideal. (I’m still having issues finding pne keyboard which support Korean output tho)
Also, as for Google home calls go, /e/ tend to substain from it a maximum, but outside bugs and issues (Wifi test address for the connection or maybe that calendar issue), it also allows users to still use it if they really wishes for some Apps, or mainly dependencies compatibility with microG.
I’ve had the idea to pull request a setting idea to implement a complete Google backlist to entirely restrain the phone to make any calls to ANY of their services, if the users opt-in from it, based on pne list i maintain, but it’s still as the stage of testing currently with my daily use if thia could actually be practical (Which it currently is.).