Quite so! And that's pretty much where I'm at: "in what sense would XS be 'replaced'"? And of course it's probably more like robustifying the API so that XS is directly used less often, or never if possible.
Note that I'm not assuming any of this is likely or easily doable. Hard things are possible, though.