As I understood during the last open source days, they differ from metanodes, that their content cannot be executed separately, only all of them. It is more like a single node.
I seem to remember the ability to lock down the contents of a sub-node being desirable to software vendors. I guess a vendor might not want to build a full plugin if their code/method can be easily incorporated using existing nodes. Or, maybe, if they do have a plugin they might also want to provide specific configurations of their nodes.
Basically, the sub-nodes are bit like the way Pipeline Pilot incorporates third party tools.