It used to be possible to get HTTPS on Chrome, without warning, without getting certificates from CA, by using DNSSEC. Nobody used it so it was removed.
That is not at all true of DNSSEC. The DNSSEC roots are fixed. If you're not trusting the same roots as everyone else, you're not really even on the same Internet anymore.
The UI you speak of is almost never invoked, unlike with the DNSSEC model where the address itself conveys information to the user in a form that even many non-technical users are accustomed to interpreting.
It is not possible to have users configure different DNS roots. DNS is part of Internet connectivity.
More information: https://code.google.com/p/chromium/issues/detail?id=50874
And in Mozilla Wiki: https://wiki.mozilla.org/Security/DNSSEC-TLS-details