> Mapping table-like data into a KV model leads to poor developer experience

This is definitely true in my experience. Unless you are literally storing a hashmap, KV databases are a pain to use directly. I think they're meant to be building blocks for other databases.