How can your browser tell the difference between:
(1)
A connection to onlinebanking.bankofamerica.com in which an attacker has hijacked the SSL handshake and subbed in a self-signed certificate, and
(2)
A connection to https://login.ratemykitten.com?
You appear to be arguing that the warning for this situation should be tuned to (2).
As suggested by the original article, the correct behaviour would be to treat it as though there's no security whatsoever. After all, logically, how is being encrypted but unauthenticated worse than being unencrypted and unauthenticated?