Historically, we've wanted actions like enable and disable to mean roughly the same things on different platforms/providers. Like Upstart decided the Right thing to do would be to fail on restart if the service wasn't running, but previously providers would still start the service. We overrode that behavior for consistency.

That said, we've been leaning more toward the "do what you expect" camp than we used to. Enable means "make the service start on boot" so it would be preferable if we could turn on without starting the service. If there's no way to tell launchctl to act that way, I'm fine with going this route under "this is how OS/X people expect it to work" path. 

I can't think of it being a problem, but we should be sure that the action [ :enable, :start ] pattern doesn't do anything foolish.