feature request - method to update resolution of --remote while still connected

This can probably be seen more as a feature request than a bug, but it has to be a common problem. I know it affects users of corp's cloud service

Describe the bug
When a user configures push-dns and persist-tun and then gets disconnected they cannot reach the DNS server to resolve --remote entries. If DNS has changed they will be stuck forever trying to reconnect until they restart the process. This is a common configuration as the same users who do not wish to leak DNS also want a "internet killswitch" which is persist-tun

To Reproduce
use a DNS server that is only reachable over the VPN (push-dns and/or redirect-gateway) + persist-tun. Change DNS for the hostname(s) in --remote. Kill old server, simulating a server migration.

Expected behavior
It would be nice if the client was able to refresh its DNS for --remote entries while still connected, so that if the VPN server migrates with the above config options in place it can still connect.

Version information (please complete the following information):
All openvpn2 versions. This was fixed in openvpn3 as of version 16_beta which was released October 2021

Additional context
This would be super helpful for corp's openvpn cloud service. This affects us.

Start by reproducing the reported setup: push-dns or redirect-gateway with persist-tun, a VPN-only DNS server, and a changed --remote hostname. Compare the OpenVPN 2 behavior with the stated OpenVPN 3 fix from version 16_beta. Done means the client can refresh --remote resolution while still connected and reconnect after the old server is removed.