It's a different threat model. Classical DNS (i.e. without port randomization and a whole host of other tricks) is very easy to spoof from all over the internet.

Inserting yourself between a client and a server is way more difficult.

Note that from the point of traffic analysis, you still don't want your TLS traffic to go through a third party.

So if your thread model mostly includes nation-state attackers then DNSSEC is only useful for DANE. If you also want to secure a lookup of, for example, pool.ntp.org then DNSSEC for A and AAAA records also makes sense.