Yes, easily. DNS over HTTPS is the most common fix for that.

Unless you are verifying DNSSEC, they could intercept any outgoing DNS queries and replace the response with whatever they want, if you are using DNSSEC they won’t be able to modify the responses since they can’t create the signatures, but they could still send queries to their own server instead of your chosen server. With either of these options they can still see what you query. DNS over TLS or HTTPS is a way to prevent all of these things, since with those you know the endpoint of your HTTPS connection is the actual server with the signed certificate and the connection is encrypted.

Edit to add: it shouldn’t matter what DNS you use to look up the IP of the DoH/DoT server, because only the real servers should have the correct private key.

Yes they can, but it doesn’t really matter. They can’t send you a faked dns response if you are connecting to the website via HTTPS, because a fake website won’t have the correct certificate.

They may block your DNS queries so you can’t connect to things, but they’re your ISP, they can block all of your traffic anyway.

The worst they can do by injecting their own DNS server is to track your queries, but if you’re not doing complicated stuff you are telling your ISP which sites you visit anyway (because of TLS Server Name Indication) and where your traffic goes (because the ISP needs a target IP to route your traffic).

A VPN “solves” all of these problems in so far as that now your ISP has a harder time tracking you, but you just moved the problem and now have to trust whoever is running the VPN server.

Ain’t that is called DNS boot strapping and it is a common practice?

They sell it as for your own safety but they are just data mining and likely selling it as it is pretty useful info for marketers.

100% possible, it’s how adguard and piholes work