Applying policy to driver start and stop "events"?

Preface: I agree it would be better to be able to process start and stop events in policy

Another Solution:
Have a loopback driver that monitors the dirxml-state attribute on the driver objects. If it changes then the driver is being started or stopped depending on the value.