I mean I've seen some weird sysex specs designed by presumably mad, drunk or delusional Japanese engineers (Casio CZ, let's all take a drink!
) but putting effectively MIDI status bytes into a sysex string as part of the message just shows a fundamental misunderstanding of extremely basic MIDI basic fundamental basic fundamentals, at a basic, fundamental, basic level. Fundamentally.
No wonder Nathan's been having a hard time with this (blame the developer!) and no wonder random people claim success or not, because the behaviour of gear handling MIDI messages outside the spec is entirely unpredictable. I mean, the system's MIDI handling, and your MIDI interface and drivers all understand the MIDI spec, and will likely reject messages that violate it, or handle them in unpredictable ways. Maybe a particular MIDI driver on Windows and a particular version of the MIDI interface firmware doesn't check and lets that $90 byte through, and the message works for Random A. Guy, and he says "it's all good". But then Random B. Guy comes along, using the exact same gear, and says "Er, no this doesn't work" because his slightly later firmware version fixed a MIDI parsing bug that (correctly) no longer lets non-spec MIDI messages through.
Terrible, terrible implementation, and Nathan is suffering because of it (and presumably many many others.)
All all because sir needs his crash cymbals to decay as expected. Maybe sell the drum module and pick up a TR-505 - that'll do it!
(If I were to guess, it's possible that Core MIDI on Macs won't let non-standard messages pass, and you're on a hiding to nothing. Windows, on the other hand, probably doesn't know or care much about MIDI, so it might let you send whatever bytes you wish...)