i considered this a couple of times, technically its trivial,
Ive done it for other similar hardware
the main ‘issue’ with the ssp/xmx is theres no access for a user to set it up, or resolve issues if it doesn’t work. (not uncommon)
so, though Ive provided details on how to do it, I dont think many have been that interested to do it.
that said, it be reasonably easy to create a module, that includes a UI to setup it up.
you can even do it with messing with scripts, which is what I did for the nebulae.
but yeah, if it doesn’t work for a user, from experience it can be tricky to resolve / support… as theres no access to terminal etc. (*)
also, Ive noticed, I seem to get timeouts/drops occasionally on both ssp and xmx, mostly on wifi, but sometimes on ethernet too.
fine for a terminal session it just reconnects, but if you were trying to sync using link, that would be a bit crap…
Ive a suspicion its probably usb power management, but I think i tried to bypass that.
… that said, Id didnt spend long looking at it, as it doesnt really negatively affect me.
overall, I decided it probably was more hassle than the benefits it provides, at least for non-technical users…
its funny, Im an Ableton user, and I do really like Link, its such a cool protoocol.
But I hardly ever use it, I guess because its just not supported widely enough, so if Im routing midi clock anyway to others, I might as well use it for everyone.
also with eurorack, I tend to use cv anyway, with a dc coupled interface its as tight as you’re going to get 
( * ) I had this with both nebulae and also organelle users, for a few, the setup just didn’t like their particular network.
I personally, found, whilst not quite as convenient, it was better to setup as an AP, less vagueries that way.
but i cant remember, if the SSP/XMX had all the binaries required to do this, would need to double check that…