High RTO for DR Failover

My Primary and Secondary Vault is hosted in Kubernetes and I have enabled DR replication between the 2 sites.

After DR Failover, I will have to make the following changes to new Primary
• Update Kubernetes auth config as kubernetes_host has changed
• Update over 10 K8s Auth Role - as the Namespace name is different in new Primary Site.

Will have to even update some of the secrets for some services. (This is a network failover. Even the DR site has all the services deployed. During failover the VIP will point to new site)

With so many changes, wouldn’t it take more time to restore the services. Is there any way to reduce this RTO?
What practice is followed for the DR failover?