This is a problem that is long overdue with the ntservices probe. The probe should have been enhanced by now to include this functionality. But I digress...
If you want to venture down the route of Application Discovery you could write a script to detect a service, attrib_publisher will tag the device if exists, a USM group can dynamically update based on this attribute value, a ntservices MCS profile can be applied to this USM group, then as devices gain X service they will be added to this group and MCS profile applied to them or as they are removed from the group the MCS profile is removed.
Honestly services it not what I would ideally use Application Discovery for as the ntservices probe should have enough logic built in to do what you want, but it's an alternative to get what you want done.
Before Knowles comes back about MCS ins and outs (putting that lite and politely), yes MCS has its issues but it is the direction everything is basically headed as we all move towards 9.x. So be forewarned you may have to work through some kinks and strange behavior to get this working.