Other stuffis not part of OpenRGB and never will be. Maybe you should have a loook at the project yourself, mainly read the contribution document.
What is your issue? Avoiding fragmentation? Yeah me to.
Currently,I do want to control my mouse, I need a different software that collides work OpenRGB.
This is not fixable by trying to force stuff into OpenRGB the maintainer clearly does not want (he said so).
After we have a working lib, with at least feature parity, I will try to convince the current maintainer of OpenRGB to outsource the device handling, and focus on the features he wants to build.
EDIT and I don't want to compete with OpenRGB, I want to focus the currently fragmented world of Linux peripheral development in a singular place, so every tool can use it. Ad a library, not a GUI application that just is another project that will die because it gets unmaintanable.
So, please, have a good look at the contribution documentation and the bug tracker. Look for yourself, or try to introduce macro support or other stuff into this project. I have done so in the past.
And to be clear: If the author and maintainer says he don't want to have this feature, I completely understand.
I know this project, and if they publish protocol documentation, I will use it. What is your point?