I agree, but as I said above, it is obvious that many entities and businesses which depend on risk assessed zero confirmation transactions for much of their functioning were caught unaware by this change. Now you can argue that is their own fault, since this has been discussed for years, but I don't think it would be wrong to give them more time to adjust their inner workings to be compatible with this change.

Having said all that, though, it isn't going to happen. 24.0 has already been finalized and will be released with mempoolfullrbf as planned, and yet another pull request to revert it has been fairly widely NACKed.