http://nakedsecurity.sophos.com/2011/09/28/amazon-kindle-fir...
I can tell you from experience 0 of the ones I've encountered outside the IT/Startup space were aware of that is what it does.
Probably around the same number who care that their traffic is going through Amazon first.
If you put it in terms they understand, they care.
https://www.eff.org/2011/october/amazon-fire%E2%80%99s-new-b...
Also, Amazon has most of its customers banking information already.
And if they pushed an update to change this [even accidentally], how would you know?
How would you know if any browser pushed an update [even accidentally], with this side effect?
2) Silk is the only one I know of that a mere coding error could cause this. It isn't like Chrome and Firefox have a fleet of machines and code designed to act as an always-on proxy.
Not many, but more than would understand or care about the "man in the middle attack browser" argument.