As I already said in a thread on that topic
To put it simply, either they follow the rules or they fork to a new coin.
If they fork to a new coin, then that wont be Bitcoin and the miners will leave.
As for transaction bias, well as long as you stay away from braiins pool who is actively promoting transaction bias,
for other pools, if the pool itself stops allowing all transactions, then yeah, people will just go to another pool that will give a better return.
Complete lack of transaction bias ensures a maximum return on mining, which is bitcoin by design = allow all transactions, highest fees get confirmed fastest.
If they fork to a new coin, then that wont be Bitcoin and the miners will leave.
As for transaction bias, well as long as you stay away from braiins pool who is actively promoting transaction bias,
for other pools, if the pool itself stops allowing all transactions, then yeah, people will just go to another pool that will give a better return.
Complete lack of transaction bias ensures a maximum return on mining, which is bitcoin by design = allow all transactions, highest fees get confirmed fastest.
The main option available (ckpool) also has a few rather egregious issues with the public version.
Rather amusing that someone is about to release a miner that will use it.
e.g.
It doesn't do block identification directly, just a floating point approximation
It reports 'luck' incorrectly as Diff/NetDiff
It's reported hash rates are quite off under certain circumstances.
It doesn't follow the bitcoin rules for block timestamps and thus can allow a miner to produce invalid blocks.
It allows mining when bitcoin isn't in sync with the network = guaranteed rejected block.
Then there's the issue of running your own pool at home, without a high speed worldwide network block distribution, that means a higher risk of losing that 'one' block you might find.
