I would love to see a UDP/TCP/Networking implementation (https://vuo.org/node/1607) as it would open up for more cross platform/application usage while waiting for proper cross platform support. I understand this might be a bit niche for most though.
Seeing that you do a lot of other work to finance Vuo, it would be interesting to see what it would cost to pay for the different feature requests. What would be cool would be the possibility to give an amount/chipping in towards getting the features implemented. Ideally, if the TCP/UDP one estimated to take a few day cost $1000 to implement, users would be able to give for instance $10 now and then until it's fully financed, or it has gained enough votes along with some financing that it gets viable to get done.
I know this could be a bit daunting as I expect it would be an estimated amount of hours, which could bite you in the behind if the estimation is incorrect. Or it would generate too much overhead from a managing perspective. Your thoughts on such a financing model would be interesting at least.
I looked into this a couple times for the list tools, but I hit a wall since it seems you can't dynamically create instances (the "memory" of a node) for a node. So while you could average a set number of "steps" in a list with a custom node, there would be no way to change it from 4 to 80 "steps" (your averaging timeframe). Vote for lists in lists, it would make this trivial.
But; what is your end goal? There might be some way to do it without averaging lists. Is it mainly audio data you want to smooth?
Can you try moving all your custom nodes out of your modules folder and then start VDMX? For an untrained eye, it seems like it crashes when it tries to initiate the custom modules. You could also open the system console to see any error messages when opening VDMX with the custom nodes present. You should filter it to something like "Vuo" "VDMX" as it can be quite crowded with messages from anywhere.
No stress! The Vuo online documentation along with the example compositions are a lot better than me explaining it though, and you can find it here: https://doc.vuo.org/2.3.0/node/vuo.tree/. I don't have a mac available right now, but I'm sure someone will help if you get stuck!