AdvisorAdvisorYeah, I really think that's the most reliable option to pursuit.
However, I've coded a DS just to see how it behaves (WinProcessStats_Responsiveness).
Just in case you want to have a look. Only problem I'm having with that DS is that I don't have Active Discovery erasing the Instances (therefore they'll stay there alarming if that process is no longer running - which is kind of what we want but, not perpetually).
This is why we're really leaning towards just expecting a number of process & alarm if it's lower that that.
