False Pipeline Status Workaround

Knowing that Dashboard and the Pipeline Monitoring API incorrectly report pipeline states after a node has been terminated (pipeline status is not updated and can appear in the Started state even though the node no longer exists, thus reporting false status), I was planning a workaround of comparing output of the Snaplex Monitoring and Pipeline Monitoring GETs to determine if any status from the Pipeline Monitoring API was incorrect. If any were found I was going to use the Pipeline Monitoring API’s POST /api/1/rest/public/runtime/stop// to “stop” the pipeline, even though its not actually executing. Should this POST work without error even though the pipeline isn’t actually running? I appreciate any info as this is difficult to test due to all licensed nodes being in use.