Minimum Fee behaving weirdly

[rafaelpac]

Description

I believe that there is something wrong with the fee estimation implemented in #5235
I cant find what it is, but the final behaviour here is that it gets a value that is not coming from the mempool.space api (is it an average?) and it also has a 10sats/vb hardcoded minimum.
The image below shows that 21sats/vb, but the minimumFee was 1sat/vb (as far as I can tell from the code, it should use 2xminimumFee).
If I try 10sats/vb, it will accept it, but not less.

Version

1.6.4

Steps to reproduce

Try to change the minumum fee.

Expected behaviour

Should accept at least 2 x minimumFee, but stucks to 10 or a number that it takes from an unknown place.