Sounds like a fun app. Seriously...I love stuff like this.
Peerlink allows the publishing of a total of 16 blocks of 16 words each. A single Peerlink station can publish 0 to 16 blocks. The data is published at about 10Hz.
So...distributed vs centralized. Great fun. In developing the Do-more control engine, I became a great fan of layering services. Creating well-defined interfaces that hide the details of how something is done and reduce it to an abstract and asynchronous 'do this', 'are you done yet', and 'how did it go' type of interface. I have many layers of state machines operating low-level objects. There is a minimum of data passing and the system is quite robust.
Not knowing the details of your app, I'm not sure how I would approach it...but...my general design methodology would likely have me looking for ways to bury the details and minimize the data flow, rather than sending all the data up to a single top level controller. I would generally view the top level guy as the conductor...he doesn't play a single instrument, he just guides those who do.
We would love to follow your progress though. Please keep us up to date!