@DiBosco
I do not know whether to count as "C++" it depends on (a) flags you pass to compiler or (b) content is C++ or maybe even file extension. What I believe I do know is if it is C++, by whatever reckoning, you cannot mix MinGW C++ code/modules/objects/libs with MSVC. So if you continue this way one side or the other of your MSVC/MinGW will have to be limited to C in order to link them. Which might suffice for some purpose of yours, but not if they are each proper C++ projects. And you won't be able to mix them if they both want to call any Qt stuff.
A lot of basic libraries supplied with Windows are C only. Although not sure, I think this may apply to the whole of Windows, certainly the "Windows SDK" stuff. That can be used. As can, importantly, the runtime libraries named something like MSVCRT.DLL/LIB which give basic start up, memory management and that sort of thing. MinGW does use these from MS/MSVC, I believe. Because they are all C only.
As for whether things provide only one compiled version, as you suggested, or multiple compiled versions. Well, like I say I cannot check, but I assume that Qt itself, if you fetch pre-compiled for Windows (as I believe you can), will supply a completely separate set of its Qt/C++ DLLs in a download for MinGW versus for MSVC? So they are supplied differently, if I am correct.
I would have thought you should pick one of MinGW or MSVC, and one of Creator or VS, and stick to that for all your work.