Hi,
you should have in mind two things regarding described steps:
1) "Then, the replication starts again, updating the VM (replicated) with the new update installed during the downtime." - this is not possible. After recovery is performed and have a recovered vm available you have no way to apply changes performed on source vm to the recovered vm. You can't start the replication again. What you are able to do (although it is not a good solution to perform every time) is to go to VR UI and remove current replication(its status will be "recovered") and configure replication again. But you will need to do this every time when you need to have a downtime for the "source" vm.
2) All changes performed on Recovered vm at the time when source is in maintenance will be lost after source is up again.
Regards,
Bobi