Thanks!
Maybe it is more clear to tell the story from the beginning.
Step 1
Reverse engineering the sysex messages and write a low level library for encoding decoding.
This is libanalogrytm and although the contributions continue it is mostly complete.
Step 2
An easy to use and embed model of a Rytm project so developers can work with a data structure which represents the model of the project in actual device. And basically has access to the features listed here.
Step 3
Use the Max SDK to write an external which uses rytm-rs (The SDK which I’ve just announced) internally and provide a nicely designed API and user experience. If rytm-rs will be used for this project then median is a good choice. One can start this project and slowly develop it and release in between until it exposes the functionality of rytm-rs completely.
There is a second way, not to write an external but provide Neon bindings which exposes rytm-rs to Node.js. This way it can be used in a Node for Max object. This would enable a lot of developers in the Max/MSP community to create a patch with it and share it with users.
Step 1 and Step 2 is completed 
We’re now at Step 3 which is relatively the easiest part technically. It is more heavy on user experience but it might get better in time.
If someone wants to start that project I’d gladly contribute and if I find time and energy I might start it also.
It was a long answer but I think soon we’ll have something on our hands but I don’t know exactly when.
For you as a non-coder unfortunately you can not use it yet.