Ok, I see where the misunderstanding is between us. Yes I totally agree with you in that example that you provide.
But the first time that i mention this:
But in any case, if you need to make a RBF or a FullRBF Transaction you only need to increment your Fee by 1 sat/vB, not by hundreds:
It was exclusively for a RBF or FullRBF option, this is to replace a transaction that is actually in mempool, in this case if you already send a 1 sat/vB and you want to change the destination address for another address you need to send at least a new transaction with the new address and a minimum fee of 2 sat/vB, so each time that you want to make some change you need to increment you previous fee by 1sat/vB MORE.
I already tested it, if you send less fee, the transaction is going to be rejected with some error like this:
insufficient fee, rejecting replacement XXXXXXX; new feerate 0.00001000 BTC/kvB <= old feerate 0.00001276 BTC/kvB
That is why I added a picture of some random transaction at that time, that transaction increments the fee like 100 sat/vB more than the previous amount. But only one sat/vB will be enough.
So again my question:
Is there some developer working for those organizations that can explaint why they do that?