CSM to Provide Capability to Preserve Data in a 5th Copy (Secondary) after Changing the Primary SRC in a 4-Site MM/GM Session

Currently, we are setting up to use the 3-Site GM/GC Session which helps us with maintaining the 3rd copy (LCP) and avoiding Full-Push exposure when region switching (PRESS) between Data Centers.  We would like to see if there was a way to provide this same coverage on the backend of a 4-site MM/GM environments?  Perhaps the introduction or management of a 5th site in a 4-Site MM/GM/GC scenario.  This session would need to allow or move the LCP (5th) site SRC between H2 and H4 (presumably the GC Targets in a 4-site environment).  If this is not possible, would an alternative be that we have a command option to start a copy session with a No Copy option "NOCP"?

Any thoughts on preserving the data between our Production and LCP environments would be valuable.  In the current 4-Site GDPS managed environment, external scripts written in-house have to be managed manually and written into JPMC PRESS processes to avoid a Full-Push to LCP.  It would be tremendously valuable to our push to replace GDPS processes with CSM processes if CSM had this advantage.

A similar Idea has been placed in the GDPS Queue as we need to figure a way to remediate internally written and managed code and scripts:                                                                               https://ibm-z-software-portal.ideas.ibm.com/ideas/ZGDPS-I-184