Would that not just encourage your average user to click through the security warnings and ignore them, potentially numbing them to other more important warnings?
Users aren't the ones who should feel the pain of a rogue CA, we need the CA to feel the pain somehow.
Perhaps it'd be better as a series of progressive informational pages than described in terms of certificate rejection. The central idea is that the site will become gradually less usable.
If a CA is being revoked, that's pretty close to the maximum pain they'll feel. But suddenly revoking a CA will cause users the most pain - I'm trying to make that gradual. A competent site would react in the first week when a few users got a mild warning, get a certificate from a new CA, then hopefully complain to the original CA demanding a refund and whatnot.
Users aren't the ones who should feel the pain of a rogue CA, we need the CA to feel the pain somehow.