Your approach for the DR plan looks correct and can be used without any changes.
You utilize Remote replica from a backups that provides you the possibility to use a single snapshot on the production VMs during processing which can reduce additional workloads on your production storage.
But in disaster situation you will need some additional time before you can start the failover process at the DR site, as you have to restore config, rescan repositories and etc.
There is a script for post job activities
, so you can perform configuration backup right after the replication jobs.
Alternatively, you can configure all Replica jobs on the backup server at DR site, so this will allow you to start the failover process instantly.
You can use replica seeding
to reduce traffic over WAN during the first replica jobs run.
The only disadvantage of such scenario is the workload on production VMs will be increased, as an additional snapshot for replication processing is needed.