yeah, I think the points you make, illustrate the underlying issue really well…
from what i see in the Organelle community, you have different ‘user’ types
- those that just want to download a patch and run it
they either cannot or do not want to edit it - those that are willing to take a patch, and use it as a starting point, and convert / develop it.
(and of course, users might be a mix between these, or move between the two for different patches)
generally, i think there are a lot more of the former AND even if they are the latter, tend to want to at least see/hear a patch, till they decide if they want to modify it.
so whilst indeed its not much effort to modify patches, i think the reality is, its a pretty small minority that go to this step 
but heres the problem…
as a patch developer, I don’t want to release (e.g.) Orac ‘tagged’ for PiSound when i know full well it can be used on any rPI… after all PiSound is ‘just’ an audio+midi interface (albeit a good one).
it makes no sense for me to ‘confuse’ other PI users, that somehow PiSound is some kind of requirement… when its not, any rPI will work.
so its a bit of a dilemma really
what does this mean? in the context of PD? what is specific to PiSound that is not true to any PI with a midi controller/audio interface?
the only specifics i know are, in/out gain which you have no control over , and a button … and with all due respect, one button is not worth coding for… you are still going to need a midi controller to do anything serious… and that is way more accessible than the pisound button 