Wouldn’t that just make it worst? Whatever automation system that are creating these spam ordinals can then just create an "inscription wall" at 50sat/vb and if no mining pools confirms them, that means all future hash rate fee will always be more than 50sat/vb.
fees are not estimated by what is the lowest-highest fee in a block..
its done by the mempool of how delayed unconfirmed transactions just sit in the mempool at certain fee levels
these ordinal supporters could bypass the mempool node routing and instead pushtx direct to pools and fill blocks with 10sat/byte. but leave a large amount of unconfirmed transactions getting relayed above 40sat/byte not confirming in next block thus causing fees to appear as needing more than 50sat/byte to get priority... even though reality would be you need to pushtx direct to pool to get advantage
..
thats said core over years have been bumping min relay fee and increments and premiumising older tx formats to make even the most leanest
1legacy in 2 out legacy not able to do 1sat/byte even if segwit done 1satperbyte
because legacy is treated as 904 weight units where as segwit is treated as 564 weight units
because legacy is treated as 226 virtual bytes where as segwit is treated as 141 virtual bytes
and core 4x the "serialised" fee for legacy but doesnt 4x segwit
1legacy in 2legacy out
Transaction size in raw bytes: 226
Transaction size in virtual bytes: 226
Transaction size in weight units: 904
1 segwit in 2segwit out
Transaction size in raw bytes: 223.5
Transaction size in virtual bytes: 141
Transaction size in weight units: 564
core also approved the bump fee default in increments of 5sat/byte instead of 1 for what they call convenience as they dont see a future of users wanting to increment on small amounts and dont see a future of 1sat/byte fees