The main issue with organelle modules not working is that some organelle patch developers are using the organelle specific graphics api. This is understandable since they are often only interested in the organelle experience.
I’ve explained techniques that show how they can support both a graphics UI and a textual UI , and also the benefits of this approach for the organelle ( eg parameter saving and automation) as well as the portability.
But as they say, you can lead a horse to water but you can’t make it drink 
I’ve considered adding a graphic api to orac, but it’s complex to make it portable - such that difficult screen sizes work. (*)
(*) I’m not really willing to use the fact that norns and organelle share same sizes.
Another option is to put the organelle graphics api in NUI and then adapt mother.pd but that’s no very appealing to me.
So it’s a bit up in the air at the moment, but under consideration- though at the moment I’m really lacking dev time. 
Note : orac 1 vs orac 2
That’s not really a big issue it’s very easy requiring minimal changes - just a matter of someone doing it