Not just interesting to keep, but crucial. It's an initializing sysex for the SC-55. As I said it contains information necessary for the proper output of the MIDI device for things such as pitch bend range and other settings (sometimes drum mapping data, but I'm not sure if SCI1.1 games utilize that functionality They don't). MT-32's sysex is more than just that as it has outright custom instrument timbres for custom sound patches. But also stores information like pitch bend range, etc. If there is sysex data, it was intended by the composer to output the music properly and absolutely needs to be preserved. Otherwise there will be missing information that affects how the music sounds.
As to what options there should be, my recommendation is this. When exporting a SOUND resource as MIDI and when choosing which music device tracks/channels to output to a MIDI file, for the devices that have PATCH/sysex data (ie- MT-32, GM, FB-01/IMFC) offer these options:
-Save without sysex
-Save sysex into output MIDI file
-Save sysex as separate .SYX file
Perhaps also having a separate section dedicated to PATCH resources would be helpful as well so you can convert them to .SYX or .MID without having to export along with a SOUND resource. That would be a nice bonus.