You are assuming that when the miners signed the HK agreement,
they already knew what the final SegWit implementation would be.
The reality is that they did not perform their due diligence until after
SegWit was released. When the miners signed the "agreement" they
signed a promise based on a design that was still being worked out.
It is very likely that when ASICBoost Miners learned that the
coinbase is altered in SegWit, they would never follow through with
the full terms of the HK "agreement".
ASICBoost Miners, in theory, can never support new coinbase
references. The issue is not SegWit, it is the Coinbase data.
your assuming that bitmain read october 2016's segwit code
and then time travels back to 2015 and made blueprints for a chip that could attack segwit..
..
more likely sceneario.. segwit is not ASIC compatible .. not the other way round.(unless time travel is possible)
end result
0.13.x versions have issues with ASIC and no longer going to be segwit compatible ..
time to wait a month and let 0.14.1 to be released and let blockstream restart their nodecount that will work with ASICS