Any hints on setting up the QTCreator environment (a link would do), I'm short on time presently, but I think this would be a good step forward for the Win toolchain.
First of all QtCreator is only an IDE without its own compiler, i.e. it uses that what it finds on your system. So, you still have to install the msvc compiler. And to save some space on your HDD you don't have to install the full VS IDE but only its compiler. Therefore download the utility "Visual Studio Installer" and follow the instructions.
Now install QtCreator. Now make sure that the LibPack's bin directory and your cmake is listed in your PATH environment. Start QtCreator and open Tools > Options and go to the first item called Kits. In the second tab "Qt Versions" add a new entry (assuming that the Qt version of the already existing entry doesn't match with Qt of the LibPack) and select qmake.exe of the LibPack.
Go back to the first tab and define the C/C++ compiler versions for the new Qt entry, select the CMake version and most important the generator. Recommended are NMake Makefile JOM or Ninja (don't choose NMake Makefile because it's too slow because it doesn't support parallel builds) and as Extra generator choose CodeBlocks.
Remark: With older QtCreator versions choosing the VS generators never worked, maybe this has changed.
Now configure the project with CMake. You can do that by opening the top-level CMakeLists.txt and running Configure but IMO it's a bit painful to do that inside QtCreator -- I prefer using CMakeGui. Create the two build directories for Debug and Release and choose the same generator as you defined inside QtCreator.
Now open the CMakeLists.txt file in QtCreator and define the already created build directories for Debug and Release.
If you go to File > Sessions > Manage you can create a new session e.g. called FreeCAD which saves all opened files when closing the project. Next time you start QtCreator choose the session FreeCAD.
Every time you load the FreeCAD project it runs CMake which is a bit annoying and it takes some minutes to parse it. No idea whether this behaviour can be changed.