The ol' "It works so let's monkey with it 'till it doesn't" scheme.
I know what you mean, but not quite this time. There was an enormous clamouring from all over the place for Audition to use ASIO, and Adobe eventually capitulated - only I don't think that a lot of people realised that there would inevitably be some limitations to this when it happened. Some of these are quite severe, and not Adobe's fault at all. For a start, you can only run a single soundcard - no mixing and matching unless you do it within a single manufacturer's scheme designed specifically for the purpose, and there are also all sorts of other niggles relating to the way ASIO channels are shared amongst running applications, for instance. Yes, it has less latency and enables you to do almost-real-time monitoring, but that's something of a luxury, really, in everyday life. It really was perfectly acceptable the way it was.
And so, if you'd left it to me - well, I simply wouldn't have bothered with ASIO at all - I made that quite clear at the time. What I would have preferred if we
had to go down this rounte was for a universal front end to be capable of driving WDM and ASIO, but that wasn't to be either. What AA2.0 has as an engine is pure ASIO, and to get a WDM input/output to it, you have to use the Audition Windows Driver - and that's less than stellar, as well.
What you could try doing, and some have reported that this actually helps anyway, is to use your soundcard WDM drivers with the free ASIO4ALL driver, which gets rid of quite a few limitations, often helps with the metering, and generally works better than the Adobe one anyway for a lot of people.