Ntp Pool isn’t running thousand of Ntp Server all over the World,if i understand IT correctly. NtpPool runs a registry for Ntp Server from Company, communities, private… To get registry entries you run a special dns Server which Response to A and AAAA requests. At the Moment this registry isn’t capable to answer on SRV requests. This enforces the community which stands behind Ntp pool with their Ntp Server to use Standard ports and provide a non encrypted interface.
Of course you can build Workarounds for everything. For example you could install Hardware clocks or use GPS to provide your own ntp Server. But it would be really cool if the dns interface from ntp Pool Supports SRV requests. This is independent from nts. This would also allow to use non Standard ports for ntp. If the community behind ntp Pool would decide to enable nts on their Server and add them to the registry or not this will Show the future. But to prevent them to register the Service isn’t the right way after my opinion.
Chickeaterbanana