5tx's of 16k sigops thats about 40 minute validation delays.
Can't fit that many sigops in a 1MB block.
It's interesting that 1MB is the biggest size you can have without it being quadratically spammy (over 10 minutes to validate). Satoshi picked a good limit.
did you not see the whole post
CORE V 0.12 : txsigops 4k blocksigops 20k = 5 tx of 4k each (total block validation time if those 5tx were created = 50 seconds)
CORE V 0.14 : txsigops 16k blocksigops 80k = 5 tx of 16k each (total block validation time if those 5tx were created = 40 minutes)
core v0.14.. is segwit.
https://github.com/bitcoin/bitcoin/blob/0.14/src/consensus/consensus.h/** The maximum allowed number of signature check operations in a block (network rule) */
static const int64_t MAX_BLOCK_SIGOPS_COST = 80000;
https://github.com/bitcoin/bitcoin/blob/0.14/src/policy/policy.h/** The maximum number of sigops we're willing to relay/mine in a single tx */
static const unsigned int MAX_STANDARD_TX_SIGOPS_COST = MAX_BLOCK_SIGOPS_COST/5;
yep more txsigop bloat is possible due to NEW limits of 0.14. which is segwit..