You may want to go under Management\Extended Events\Sessions\AlwaysOn_health in SSMS and view target data on the package0.event_file and check for any state changes around the SCOM Alert time frame....
If I were in this situation and wanted to stop the replication, I would just stop SQL Server on the secondary. Once the restore process is broken I've not...