Let's look at just a couple of your devices as an illustration:
The 0x4B device has 120 route changes. But at the same time, RTT and Neighbor count are great. The implication is that the route that is actually in use is not very reliable and the hub is trying alternates. But there's only a very few alternates.. between 2 and 4 routes fit into the space allocated inside end devices. It means you may have tried all four 30 times already. Don't try and fix this yet, but it's probably a good 'canary' and as you fix other things, this may improve.
Don't expect instant gratification from clicking Remove. All of the work is done out on the radio and the hub just waits for a message. The hub doesn't make us wait, it pretends its done and refreshes the screen. IF the radio finds that the device responds in any way, the remove is cancelled.
Compare the RTT and Route Changes on 0x4C and 0x4D. Those are good numbers BUT the speed is 40K (far right column of your screen shots) That might mean the signal strength is causing the device to knock down the speed once. You'd expect Zwave + to run at 100K. You even have a couple running at Zwave's lowest speed: 9.6K
Start with devices where the Route column is blank. Then move to the ones with Discover. Once you solve those, let the mesh settle for a few hours. You should se improvement with each device you cure.
