"""I think it is because you force the iphone by using your dns-proxy and don’t allow it’s using it’s own direct secured connection. """
That makes sense. Confirming, that the big bros like goggle and appel continue in their efforts to force the users under their secure (???) umbrella. To make shure, nobody can escape their advertisements, not to hurt their business. The forced usage of https was the first mayor unpleasant hit, because it practically eliminates the usage of web-caches and made content filtering harder, costing much more bandwidth, i.g. to be payed by the users.
Yeah, if you'd install some local DNS -> DoH proxy/VPN app (don't know if those exist for IOS, they do for Android), it'd probably still complain, even though everything is actually very secure.
OT: you could also see it that way that the network you are in is tracking your dns queries.
The iPhone does not know if the LAN DNS Server/Proxy is secure. It just informs the user that the current network does not allow secure dns from the enduser device to the internet. And of course all those apple services "iCloud Private relay", "do not track" etc ... uses this in some kind. E.g. if you enable the "Tracking of IP-Address" in the WIFI Settings.
I find your arguments interesting: https is bad because no content filter; apples information about forced dns is bad because of NSA
https bad: In every school there must be a content filter for the minors. Forced DNS must (most likely) be shared with NSA. I consider them to be able to decrypt.
You setup your iPhone to use the above profile,
also configured your router to use a custom encrypted dns
and the iphone complains about blocking encrypted dns traffic,
so set in the iphone in your wlan settings set the dns server to manual and point it to your router