I haven't tried a 'replace' with 2.2.3.132, but I have more than a few times with previous 2.2.3 It did work. I'll give it another try later, but it was quite exiting to do those previous times. 
What I did was replace a device with itself... I Joined a device, then using another Hub, I excluded it, which does not alter the original hub. Then I waited for "Failed" and clicked Replace. I put the device into Include, and it did.. although the UI needs some beautifying. 
OK, UPDATE:
Works.
I took an Aeon MultiSensor 6 I have paired to my C-7. I hit Exclude from one of my other hubs. The device and hub both agreed that it had been excluded.
Then I just had to wait for the C-7 to detect the loss. To accelerate it, I did a Configure which sends a few dozen ZWave commands to the (now dead) MultiSensor. Those fails convinced the Hub the device was Not Responding. I clicked Refresh and it came back as Failed with the Replace button available. I clicked Replace, and pushed the button on the MultiSensor. The LED on it indicated it was conversiong and the hub rather more quickly than I was expecting announced "done" -- logs blew by responding to all those jammed up Config commands, so it's very clear it's talking.
Beautification = Stop Replace when it's saying it's stopped?, and Status of done is not as exciting as say... "Replace Successful"
One factor to mention is that the Type reverted to Hubitat's built-in Aeon MultiSensor 6 driver vs the one I usually use and had selected prior to the repair: AeotecMultiSensor6. This is, I believe, as it should be...
Replace is nothing but a normal Include with a specific Node Number vs "next". Which means I could have replaced the MultiSensor with a Dimmer, theoretically and therefore, matching the driver to the device is the right thing to do.
