True DNS over TLS support for PR60X

Companies like AdGuard, NextDNS, Control D, etc. use a unique identifier address (like tls://123456789.d.adguard-dns.com) to distinguish a user's particular account and allow them to filter DNS according to the user's account settings/rules at the router or device level. The PR60X does not support entering a custom DoT-specific address to accomplish this. Thus, it seems like the only way to do DNS filtering is through generic DNS IP addresses for each WAN (IPv4 settings section). That isn't really DoT so it seems like the PR60X isn't really doing anything when "Secure DNS" is selected and a DNS provider is selected from the drop down. Maybe it is just kindly passing through device level DoT? But I didn't buy this semi-expensive router to still have to enable device level TLS on each device. Kind of misleading and a little sketchy if you ask me. Could you add the support for the custom DoT-specific address to enable DoT at the router level (as opposed to device level)?