easy ones first...
search on here for clock divider, there have been a few. common (easy) approach is to use a counter, drive by square lfo, then a logic/decode
5 into 1 = mux 5
next ones, sometimes midi mapping will work... or using mod sources to control things (like selectors)
at other times, midi control is more important than the UI.. i.e. your not using the axoloti UI at all.
in which case, I tend to use tables... i.e. i receive midi input (or other sources) then store values in a table, which then I then use as a source for the 'gates/notes' rather than a selector.
if you look in the Jan competition at my patch , you will see I follow this, albeit driving it with random signals rather than midi (as that was the purpose of the competition)
personally, Im moving away from using the graphical objects in Axoloti, for the simple reason, I usually use patches with the Axoloti UI running.
(though I do use dials and things, currently as some things can only be altered via dials as we don't have inlets for everything yet)
btw, this pin matrix, if you want graphical input, Id just arrange a few objects on the UI as a grid.
but bare in mind the VCS didnt just have on/off, it had variable values, i.e. id use an array of dials.
my main advice though is to jump in and start patching... might seem daunting now, but the more bits of the puzzle you patch, the more ideas of how to get around things will come to mind.... and of course showing patches here, will get comments about to solve problems, or how you can improve things.