@bitbee99 intent and motive and ability go hand in hand.
If we had no transaction limit and 70% of the hash rate was turned off, the network should continue at the exacts same transaction capacity, what would change is the rate that blocks were produced, and the number of transactions in the block and the time to confirm a transaction.
This threat has shone more light on the fact that we should not have a transaction limit. 100% of the hash rate that is provided to secure bitcoin is voluntary - it is not guaranteed, it can be turn off at any time.
Antbleed is a name given to a feature that was extensively requested by miners when ASIC's were first introduced in 2013 there were lots of devastating thefts. How the feature was designed was very wrong, it's a centralized system that can fall into the wrong hands. Fortunately the hackers are not competent enough to actually execute a MITM an attack, they actually required you to point the device at an IP in their control.
The criticism of such a bug is positive, the response to fixing it is also positive. Antminers have 70% market share they could have refused to fix the bug and given a bunch or reasons to keep it and made it more secure but instead they chose disable it - the best possible outcome.
The developers on the other hand have control of the software client used on the network, they insist on keeping one of bitcoins most devastating bugs - a transaction limit, they console the software that makes that bug dangerous, they just keep making up reasons to keep a transaction limit in place.
stay skeptical, keep rational.