It is a work in progress reply. As all the time various solutions are welcome.
The -mempoolfullrbf choice when set to 1 ignores RBF signaling and assumes each transaction might be RBFed. This feature was launched in Bitcoin Core v24.0 though it was off by default in 24.0. For extra dialogue on the introduction of the mempoolfullrbf choice see this query.
If the default mempool coverage in Core was set to mempoolfullrbf=1 then one would assume that inside 1-2 years the vast majority of Core nodes (and the vast majority of nodes on the community) can be working this coverage (after they replace to a brand new model). After all customers have the choice to vary from the default however in actuality most appear to run with coverage defaults.
The V3 Coverage proposal introduces an further algorithm to current standardness and coverage guidelines (V2 Coverage?). This consists of RBF signaling so it appears to be continuing assuming that transactions do nonetheless have to sign that they’re replaceable and we aren’t assuming a community of nodes working the mempoolfullrbf=1 choice. Even when the vast majority of the community was working that choice one would assume there can be a minority of the community checking RBF signaling guidelines have been being utilized appropriately.