Talking about the design, the further we get from 2012, the more obvious it becomes that windows 8 was kinda like the bauhaus movement for an operating system that wanted to be on touch screens but was made to work on traditional mouse-keyboard interface. It was technically correct, aesthetically pure but socially rejected because it was too stark for the general public (my opinion).
This implementation gets one thing most Metro clones miss, i.e the typography as structure paradigm. In Win8, there were no divider lines or heavy drop shadows to denote hierarchy. The hierarchy was defined strictly by the weight and size of the font.
We spent the last decade drifting back into glassmorphism and mica materials (win11) because people missed the comfort of texture but from a pure information density and rendering performance perspective - the flat, monochromatic 2D plane of windows 8 is a nice tangent. It removed the cognitive load of decoding the UI chrome for touch users.
ps: I'm impressed by the constraint of using native Qt/C++ here instead of taking the easy route with electron or QML/javascript bindings for everything.
The cognitive load it's trying to guess where the button lies in the interface for flat screens. Not an issue under GTK2/3/4 with Zukitre (and QT5/6 reusing it with qt5ct/qt6ct or with an environment variable setting QT_STYLE_OVERRIDE to "gtk2" or similar.