It would do something meaningful if the dev team would've treated inscriptions as an exploit and released a security patch with ordisrespector turned on by default. Then it'd be just like any other standardness rule, like the 80 byte limit on OP_RETURN, or the dust limit of 546 sats. You can still get non-standard TXs mined but it doesn't happen by default, which is enough.

Individual node runners patching their nodes won't mitigate the issue by themselves, but building a modded Bitcoin Core is a good learning exercise that shows that Bitcoin Core is not a consumer product given from above, and that you can use it to show your preferences (staying within consensus).

The bogus fee estimates are the #1 criticism I get but it's not a problem in practice. Normal transactions usually dominate the fee market, and if they don't it's trivial to get a second opinion. Miners accepting non-standard TXs off-band, or Mempool's TX Acceleration service probably do more damage to fee estimates than ordisrespector.