It’s still slow to start up. That’s partially because of .NET in general. There is a lot of code to read and JIT before a .NET application runs.
.NET apps can be published with AOT code (ReadyToRun). WPF apps are still pretty slow to launch with ReadyToRun enabled; I haven't profiled it to see why, but I suspect it has a lot more to do with WPF (somewhat abandoned for a decade, and the XAML bits have always been slow) than .NET.
In my experience the JIT penalty at startup isn't as bad as people think, the .NET JIT compiler is really fast and the average console app is very quick to start up.
That's just revisionist marketing
It is worth noting that WPF can run on this latest version of .NET
FWIW it was only recently migrated to a modern .NET version, give the latest version a spin if you haven't already.