Hey bigkeoni64,
yes this should work, but you have to make sure there is no typo, as the moment you change the HA password you lose access to the secondary via 'execute HA manage' and will only regain it once the cluster is reformed with the new cluster password - and the cluster can't reform if there is a mismatch/typo somewhere.
What you could consider (to substitute for onsite), is to setup individual HA management for each unit - that way each node would have its own IP you can access individually, and you wouldn't lose access to the secondary even if there is a mismatch in the password for some reason.
An example: https://docs.fortinet.com/document/fortigate/6.0.0/handbook/234765/out-of-band-management
Either way you should make the change during a maintenance window, as there would be a short time the cluster can't connect to each other, which might mean both units consider themselves primary and you have a split-brain scenario temporarily, until the cluster is reformed with the new password.