Since you say you haven’t found this much of a problem in practice I thought you might find my experience interesting.
I just ran into this after I migrated a largish Android project to Kotlin. There were a handful of overridden fields, some with only getters, some with only setters. Android Studio doesn’t give any indication (that I am aware of – maybe I missed something?) that I might need to override both getter and setter in order to call super, it just said “Property must be initialized.” So I did, and then I had a lot of fun hunting down the bugs resulting from the fact that the super’s getter or setter wasn’t called.
The fact that you have to create both getter and setter in order to call super is only a mild inconvenience, but the fact that you can seemingly side-step this requirement by adding initialization, AND that this introduces (from my perspective, anyway…) the side effect that the super getter/setter won’t be called is pretty surprising, IMHO.