This particular problem has been solved for a long time, there is no need for this check for CC compatibility or any others, nor will there be in the future. See: Making Extension Plugins Compatible with Classic Commerce - #4 by james
We should keep wpautop if we want people to be able to easily and successfully upgrade their existing sites from ClassicPress v1 to v2 (or v3 or whatever version number it would actually end up being).
If you disagree with this then it shows that you have not worked on a platform like WP/CP at scale, with practically infinite variations in how it is used and what other code is frequently running along with it and depending on the current behavior, bugs and warts and all.
Do a search on the forums for “wpautop” and you will see some examples of the kinds of unexpected breakage that occurs when disabling wpautop. It can be done today; you should try it on your sites. Just not in production.