thats maths cludge OUTSIDE of network consensus rules..
but from a network consensus rule its what you think
No. The 4x sigops counting for legacy transactions is enforced by SW rules.
pools can ignore the 4x sigop count just like they ignored the priority fee formulae. by not following all the wastful cludgy maths stuff outside of consensus
which is where your hopes and expectations lay..
thats why having <4 maxtxsigops in the consensus.h header file would solve the issue so easily
maybe best you spend more time managing sig-spammers and taking a cut.
because you have made it clear you wont take time to learn c++. and prefer just to spam topics with empty word baiting for an income