these are great ideas to explore! this collection of devices isnât meant to box in, but to provide a framework for folks to build their own unique use cases 
iâd say just rip into this! youâll want to go through the druid studies to get a handle of the syntax and go through the [crow] objectâs help patcher in Max to see how to apply that syntax inside of Maxâs visual coding environment. I cannot recommend Matt Wrightâs Kadenze course highly enough. you will walk away with a full understanding of how to program in Max, for free 
you can ping here for help if you run into any specific questions or hurdles, and you can share any helpful snippets you land on here: ^^ recipes: max / m4l snippets for crow
yes, though depending on how much traffic youâre sending you may find that you can only do 3-4 channels.
1 command center per crow. you can load as many of those m4l devices to speak to one crow as youâd like (or until things get unstable, depending on how much stuff youâre slamming into the stream), which all route through a single command center.
soâŚ
âŚthis is pretty much already possible using other MIDI-generating/affecting M4L devices ahead of 6 jf_vox devices each set to speak to a different JF channel! itâs totally valid to build a group of jf_voxâs and set them to receive from the same MIDI track and throw a few of Liveâs MIDI Effects ahead of the incoming MIDI on each channel:
this sorta stuff extends the crow devices so much â i always have a Random ahead of my jf_voxâs 
hope this helps! let us know where you get to!!