Actually, just use inline mult widgets. This build is right on the edge where I would say to not have the mults in a build at all due to space constraints.
Most of the time, a sequential switch is what you'd use to switch between sequencer rows (such as the Moog 960 and the 962) by sending end-of-row signals to the switch so that the next row is, say, row 2 or 3, then back around to row 1, etc.
However, they DON'T have to be used for only sequencing. The ARP 2500's Mixsequencer is an electronic switch-type device that can scan across several incoming audio signals and change the inputted signal each time your clock sends a pulse to the Mixsequencer. But you can do the same thing with most any present-day switch; feed four audio signals into the switch's inputs, set up your clocking for it, and then send the output to whatever audio destination you like. Same thing works with control signals, too.
In the test gear world, these devices are referred to as "multiplexers"...several signals go in, clock steps through the inputs, and the result is a single output consisting of whichever channel is selected by the multiplexer. Same idea applies here, also. One that could be fun is to send differently-divided clock signals that can then cause a sequencer to jump around in time with the switch's selected input. LOADS of that good ol' "abuse potential" there...