I spent quite a bit of time mucking around with the AWE64 Creative software.
I can see now why Creative tried to render CTCU useless from MS-DOS mode. When you have Windows, which is a PnP OS, you are supposed to configure the resources in Windows. When you run CTCM and DIAGNOSE these changes will be applied to DOS.
Changing resources in Windows and DOS could lead to problems.
So what about users who just use MS-DOS 7.1?
Well if you built your MS-DOS 7.1 installation from a W98 SE bootdisk and manually transferred files from an existing Windows installation there won't be a winbootdir environment variable and CTCU will work just fine. So will INSTALL.EXE which is a bit odd but I've seen it time and time again.
So this leaves MS-DOS 7.1 users who installed Windows and then hid or disabled Windows through entries in MSDOS.SYS. As they can't go back into Windows and have winbootdir environment variable, they do indeed require a working CTCU.
Note that there is also mention of Intel's ISA Configuration Utility (ICU), but I've never seen one.
I used to create MS-DOS 7.1 installations with boot disk and manually transferring files but now that I learnt a bit more about the whole thing I just installed W98 SE on my Pentium 100 Time Machine PC and configured MS-DOS mode as per recent video / tutorial and used CTCMBBS and 95DOSAPP to get it working in MS-DOS mode.
So if you have Windows on your machine there shouldn't be any reason to touch CTCU. Configure resources in Windows device manager.