Before Google switched over to Wallet and allowed responses to reviews, you could get a fair bit of info about each sale (for a paid app), including often their email address.
I would often email people seeking clarification when they would review "XYZ doesn't work for me" in a bid to fix it.
On one hand it might seem a bit creepy, but on the other hand, they were my customer and I was provided with information about them. I never asked for a better review, just for information to improve the product.
They rarely replied.
Developers shouldn't be so concerned with reviews. Reviews are for other customers, not for developers to read. I say this as a developer who has received reviews that contain misinformation about my product (lying that it's going to be pulled from the App Store, for example). I made a decision to stop reading reviews and just focus on building something I'm proud of. This has paid off for me.
I also make it easy for customers to email me directly in my apps. I get a lot of good feedback this way — and I can send a response that is actually solicited.
I'm the same though, completely averse when it comes to looking at reviews, good and bad. I hate it.
Your last point is really good, I've always thought there should be super easy mechanisms like this (although I'm often guilty of not providing, aside from email address or Twitter handles).
The Google Maps feedback mechanism works really well - includes a screenshot and a bunch of diagnostics info. The only thing I don't like about it is you need to shake to trigger it, meaning most people don't know about it.
We currently have reviews implying that our dictionary is missing basic words when in fact I think many people would think there are simply too many words that are valid in English and will surprise people.
Review replies would at least improve context even if it didn't change the ratings themselves.