Unticking Cmake Tool in kit settings filter effectively disables CMake

It's all too easy to render a (CMake-based) kit unusable by unsetting "CMake Tool" in settings filter. Actually, I was under impression that the setting filter would hide the setting rather than completely unset it. This is especially puzzling when CMake is in PATH so you can literally go to the terminal within Qt Creator and call it. It's also confusing when you have a non-empty CMake Configuration for the kit (which is typically the case, with the C/C++ compilers being propagated from the kit): the CMake Configuration remains there and is enabled, leading one to believe that CMake is enabled for the kit.

To reproduce:

1. Find/create a CMake-based project; configure and build it
2. Open Settings/Kits, select the kit this project is built with
3. Open Settings Filter; unset CMake Tool; close it
4. Close the settings window.
5. Restart Qt Creator
6. Observe the infamous "No suitable kits found" message, with the previous configuration falling out to "unsuitable" ones.
7. (Optionally: open the kit settings again, enable CMake Tool, close the settings, restart Qt Creator, find that you now have to import the previous build, and then go through all the configurations to remove "(Imported)" postfix appended).

What I would expect is either clear feedback that CMake is disabled by disabling other CMake-related settings in the kit configuration; and/or, given that CMake support is on par with qmake these days, and we also have Meson around, make the build configuration tool a multiple choice.