mentioned in: bitcoin#32463

"> If you re-touch for any reason it would seem a little more logical to me to slightly restructure so we test without new minrelaytxfee first (check_estimates() on L260), then add the high minrelaytxfee before doing the rest of the tests with it added. But zero practical difference and not a blocker for me.

Makes sense, I will add it in the follow-up to this which is retaining the original feature_fee_estimations.py tests behaviour by incrementing the customblockmaxweight by 4000. see bitcoin#32461 (comment)
" - ismaelsadeeq