@bflad (Hi Brian) once told me that SetNested objects containing both configured and computed objects were bad news.
You might find that thread (and the linked response in particular) helpful.
I don’t understand the hash thing you’re pointing out in the AWS provider, but I’ve really been wishing for a way to declare a “key” attribute in a SetNested attribute. Maybe that’s what you’re getting at?