Yeah that was what I was thinking at first, at least that is what you would come to expect when accustomed to working within the UI. It is the typical pattern, and it would be nice.
Kubernetes is a pretty complex beast though so I guess it would be pretty difficult to control expected behavior with a toggle switch in the settings services table. The things is it would have to trigger a series of jobs when toggled, which could lead to the switch getting spammed and cause further complications, I suppose. It could maybe work if the switch was grayed out until the previous on/off job was completed.