Uno is a trap. It will take just as much effort to convert to Avalonia, which is what you should do if you want it to remain a desktop app. We tried all of them, and Avalonia is that one that truly felt like a spiritual successor to WPF, plus the maintainers are practically non-toxic and willing to help people, which in this day and age of arrogance in FOSS is really truly rare. With the release of v11, the product has really become mature and stable/fast. The styling system is more CSS like, but once you get a hang of it (specially if you use animations), it actually makes more sense than the WPF one.
But the biggest issue you will have is not really the technical complexity of different toolsets, its the lack of 3rd party support. If you use and depend heavily on 3rd party controls like Telerik/Devexpress/Infragistics/etc for WPF, you will be in a pickle no matter which path you choose. There is simply no interest in porting their WPF products to other similar platforms by any of them (at least at the time of writing this, in case they decide to wake up in the future). Even Uno support is very limited and scarce. Its the penalty we accepted by migrating, there are (pretty good) community alternatives for the most critical components but you will have to give up on some visualization depending on the nature of your app.
