Hi,
Could there be timing issues with this approach? If you have 10 nodes dependant on 1 switch, all with a status interval of 1 minute, you're bound to have some nodes going down before the switch node.
If it's turned in to a full-fledged rule, it'd be really cool if the rule could trigger the status (or more generally, any random DCI?) to be checked before evaluation; but perhaps to prevent it from bogging down the event processor make this optional.