There is also DNS over TLS. DNS over HTTPS is basically DNS over TLS, but with workaround for port blocking.

You can't condone it because you'd prefer "DNS over TLS" or a you have a notion that DNS shouldn't have other headers before it because it's a core protocol and should reimplement the functionality it needs frome TLS?

In the case of the former I agree, the browser should be doing this over TLS as HTTP isn't giving any additional protocol functionality. In the case of the latter the purpose of protocol encapsulation isn't that the most important comes first it's that you can abstract service layers instead of remaking them for each new thing.

I think the main reason this happens is because SSL is a pain to configure and develop and it's easier to just use HTTP's SSL than to make an SSL version of everything else.

It wouldn't be my first choice for a lot of reasons, but HTTP2 is getting pretty close to just being a binary protocol anyways.