The idea of adding value quantization as an option to the editor is interesting. However, I'm afraid of it being non-obvious and possibly distracting for new users if not implemented properly. "Why can't I draw smooth lines??". The controller framework is purposefully generic, but that doesn't mean it cannot be smarter. The primary issue here is that the controller can drive multiple automatable controls, even those of other controllers. Therefore, there is no "one true discrete value set" for the LFO's base knob.
Having said that, the problem is simplified if only one controller is connected. Perhaps some of the LFO's knob's parameters can inherit those of the controller if only one control is connected. If multiple controls are connected, then perhaps it can inherit the values if all connected controls share the same discrete values. If the controls are all discrete, but do not have the same discrete values, then maybe a union can be used. If any of the connected controls are non-discrete, then the controller's controls must remain non-discretized.
An interesting experiment, but not something I see myself getting into soon. I do not know if controls have the ability to change their min/max-value and to signal this fact to other objects off the top of my head. This would be required as the controller is connected to additional controls. Comments?