If you have to deal with all that baggage, then you might as well go build the UI layer native.
https://wiki.qt.io/Language_Bindings
5.1 Qt for Python (PyQt)
5.2 Qt for Ring (RingQt)
5.3 Qt for Rust (Rust-Qt)
5.4 Qt Quick for Rust (qml-rust)
5.5 Qt Quick for Rust (qmlrs)
5.6 Qt for Crystal (qt5.cr)
5.7 Qt for Go (qt)
5.8 Qt for C#/Mono/.Net (QtSharp)
5.9 Qt for C#/Mono/.Net (Qml.Net)
5.10 Qt for D (QtE5)
5.11 Qt for Haskell (qtHaskell)
5.12 Qtah
5.13 Qt for Julia (QML.jl)
5.14 Qt Quick for Haskell (HsQML)
5.15 Qt Quick for OCaml (lablqml)
5.16 Qt Quick for Node.js (Brig)
5.17 QML bindings for Nelson language
And the only churn was a change about five years ago from a less pythonic API (using wrapped Qt types for most things) to a more pythonic one (using Python's native types where it makes sense). And that wasn't even that bad. Other than that it has no more churn than Qt itself does.
With it, you have the full power of .NET Core and QML. There really isn't any limits.
the only true "cross-platform" alternative is electron, which is a bit bloated and slow, but vscode is built on it, along with many others and worked fine. I personally prefer electron these days.