I believe lfo's, envelopes etc are good use cases for control rate. If those would be events-at-control rate, you get "hot" and "cold" inlet design philosophy like PD or Max.
One advantage of events is that it avoids re-computation at k-rate of (pure) functions whose input didn't change. However in real-time it is the worst case scenario that causes buffer underruns. Saving control-rate re-computations could optimize the best-case but create higher peaks in dsp load, when simultaneous events happen.
There is some sort of event functions in Axoloti though! Parameters have a "pfunction", this (pure) function can pre-process a (user friendly) parameter value into what is needed in the dsp computation. "pfunctions" aren't exploited at maximum yet.
"pfunctions" are triggered by manual parameter changes, modulation sources, MIDI-mapped parameter changes, preset recalls, or "scripted" parameter changes.
I believe this execution model is very similar as used in commercial fx processors, or synth engines. Though I'm not 100% percent sure, I haven't disassembled any :)
I believe the variety of patches shows this execution model is quite flexible and friendly.
I'm open for discussion, but please be a bit more clear - if you're reacting to some piece of documentation, please quote or reference.
Are you speaking from theory or practice? Are you a PD addict looking for trigger, spigot and moses objects? Or other software/hardware? What are you trying to do?