We need to ensure that anything which requires a service is itself a service. ServerDeploymentStartStopHandler sidesteps all boundaries. It's not a service, nor is it part of the model or a model update.
I think that once we finish the MSC upgrade and revisit the deployment chain services and detyped management API, this issue will probably resolve itself though.