If you do what you wrote the two SRM instances would be in 2 completely different states.
- One thinks things are as before (VMs running at the Protected site), the other thinks that workloads are now running at the Recovery site.
The second SRM server has the more accurate view of what the state is because changes have been made to it later than to the protected site. As p_hall outlined the only way to recover from the split in SRM state is to go through the steps shown. To revert things back to how they were prior to running the failover would require deleting all effected protection groups and recovery plans, powering off and removing all recovered VMs from inventory at the recovery site, reconfiguring replication (unmounting datastores, removing datastores, redirecting replication to flow from protected to recovery as at that point both sites would be separate and in R/W state), and then reconfiguring SRM again.