we like to drop .NET Framework dependency completely and make our app self-contained running everywhere on all computers. We already did that with another application and it was a huge success. At the moment lots of support inquiries we receive are all .NET Framework dependency related, this costs us a lot of time and money. This is why we would like to not going the way of .NET Framework / .NET Core mix-up, although you are right this is currently possible. So you are right that pre-compiled .NET Core 3 assemblies are mandatory and should be distributed either side-by-side or by separate installer.
I see a lot .NET developers porting their software to .NET Core and I agree with Miguel the rapid development, massive improvements and the fact that its open source are the main reasons but also that, although Microsoft said they will continue to support .NET Framework, all new features will be mainly .NET Core exclusively.
Maybe in the long run you could take a look and see if WPF Studio can benefit performance whise from all the new features in .NET Core like Span<T> or hardware infragistics but at first and especially as long as .NET Core is not a final product pre-compiled binaries without any changes should be enough.
Thanks for taking a look at it, we are really looking forward to it.