To be honest, this could just be the AMD rep misunderstanding/misinterpreting the situation. It has happened before.
This isn't the first time an AMD rep has done something like this.
VSR or Virtual Super Resolution was introduced with AMD's Catalyst Omega drivers, 14.12 for the first time. It's support was limited to AMD's R9 290/290X initially, and was added to Tonga/Fury cards later. Though the Fiji and the Tonga cards could VSR up to 4K, the Hawaii cards were only limited to 3200X1800. AMD's official response was that the older hardware lacks hardware scalers, and that the support can not be ported over to them at all/same extent. Sounds legit.
..till, some people managed to figure out registry values and enabled VSR on older cards, the HD 7000 series to be specific, and even though the HD 5000/HD 6000 series of cards didn't officially have the option visible in AMD's Graphical Control Settings, they had the ability to use VSR too. Only then, AMD's official response changed. But shockingly, one of their reps said that they will be bringing support for VSR to only R9 280/R9 280X cards, and not on the older HD 7000 cards, and that R9 280/280X cards have this certain scaler(!) present that the HD 7970 doesn't. Then people literally ripped him a new one, and eventually VSR support came to HD 7000 cards too.
So, I wouldn't say that AMD won't fix the issues just because on of their reps said so. But if what the rep said is the approach AMD's taking, undoubtedly, it'd be a step backwards.
Update:
S3r1ous over at Guru3D forums has managed to find something that could also be the cause.
Apparently, The Windows 10 OS Update,
KB4051963 (OS Build 16299.98) brings the following changes/fixes:
So it might be worthwhile to update your Windows 10 installation if you're facing issues. Though that still doesn't change the fact that the crashes go away when you switch to an older driver, and the appalling response from AMD's rep.