lol OP's proof
.. a tweet starting "i heard"...

hmm wheres the salt

asics have been around for 2 years
asic boost as been around for 2 years

segwit code 6 months
gmax found flaw in segwit codes incompatibility 1 month

drama today is not caused by actions of asics. but speculation.

asic manufacturers did not make a time machine to make a segwit nuke
segwit just wasnt made 'soft enough' to not cause issues.
and gmax just a month ago found an issue where segwit is noft soft enough to work with 2year old hardware and efficiency technique.

solution
fix segwit to be even softer.
or
fix segwit to actually be implemented as a proper node CONSENSUS along with other community required features(dynamics, lowered max txsigops), thus only need 1merkle and get other needed features in. and finally get the community what it wants

stupid part is even with lots of pools abstaining objecting(70%) the fingers are being pointed at 16% and even blaming temporary price drama on that pool even when the pool has not done anything different for the last 2 years