You can’t run a max/msp patch on the SSP, because there is no max/msp runtime for linux as far as I know. You can generate DSP code in max/msp using the gen~ object, and this code can then be turned into a module which you then could load into the SSP’s software (when the SDK is available), or you could turn it into a standalone application you can run on the SSP. But all that assumes you are a developer or have developer skills.
If you are not a developer and want to run something like Max/MSP on the SSP, you can run PD (pure data), which is like max/msp but open source. That requires some familiarity with linux. Basically how to install linux/debian packages, how to configure audio in PD, etc.
If you want to install and run PD or any other linux software on the SSP, then yes you need to learn the basics of the linux command line. Other examples of synthesis software for linux are supercollider and csound.
So the reason we are building an SDK for the SSP, is to let developers easily wrap their existing DSP code (from a VST instrument for example) into a module which can be loaded on the SSP. This makes it possible for you, the user, to access a lot of great modules and DSP plugins or instruments on the SSP.
Of course, our software that comes with the SSP, is already a “complex synthesis environment”, so out of the box you don’t have to install anything, it just works. All we need to do is develop more modules but there is already a good selection available in the software right now.