I think an #Ordislow implementation is still a solution to balance the exploit of arbitrary data into the Timechain using the SegWit discount.
https://www.nobsbitcoin.com/mempool-acceleration-marketplace-upcoming/
Though the inscriptions situation is taking too long with low perspective of self resolution and Bitcoiners are starting seriously to take sovereign action in their power to op-in in any Bitcoin Core version they wish and give added value. 
#[1] 
As measure against SegWit discount exploit.
That is the reason why transaction fees do NOT “buy” space in ROM memory (SSD); instead is a compensation to the miner for his/her marginal competitiveness loss due to a marginal addition of a transaction.
A #Ordislow would better balance an opportunity cost & SegWit discount. 
That situation is always possible even without #Ordislow. Participants of the Bitcoin system should know the concept of “confirmation” and evaluate how many confirmations they consider safer.
For instant payments; the choice to use would be lightning.
And if mining node operators process non-inscription transactions, then the entire Bitcoin system works as before; #Ordislow would not be active at all, thus no effects as #Ordislow would never existed.
There is not censorship in Bitcoin system as long as Bitcoin regular nodes and mining nodes are decentralized. I personally, do not worry about that aspect or narrative.
#[4] #[2]
There are some hints that #Ordisrespector (Luke’s patch) and mempoolexpiry=24 have an effect degree pursued by #Ordislow.
Though a real #Ordislow could reduce the incentives and increment the opportunity cost for processing inscriptions at mining pools (thus, miners).
What would be your opinion about #Ordislow Luke? 🙂