WPF should cost too many time to parse the xaml during startup. In UWP, we can build xaml to XBF that the binary representation enables performance advantages versus loading and parsing a XAML file as text.
WPF actually already does this, but not to XBF, strictly speaking. WPF uses BAML, which is a similar technology, but not the same file format as UWP's XBF.
In WPF, it is compiled into a format known as Binary Application Markup Language (BAML). In Windows Store and UWP, it is compiled into a format known simply as XAML Binary Format (XBF).
When presentationbuildtasks.dll and presentationframework.dll projects get added to this repo, take a look at the baml writing and baml reading code...and consider improvements.
I am not deeply familiar with advances that xbf made over baml, but there could be some?
According to some performance tips from MS targeting XBF2 (which is a new version of XBF) 'reduces the disk footprint of a XAML file' (over XBF1) and also 'improves the heap and object creation costs'. So there's those benefits at least.
Most helpful comment
WPF actually already does this, but not to XBF, strictly speaking. WPF uses BAML, which is a similar technology, but not the same file format as UWP's XBF.