That's the wrong solution to the problem, as it means learning a second kernel and all of its stuff and making compatibility shims, whilst still facing the real problem that is not software at all.
The right solution is actually explained the headlined WWW site, where Peter Tribble points out (in the About page and in the Use guide) that the significant constraint is that xe does not own the actual physical hardware to develop against. It's the usual story with small projects: good donated hardware, and developer time (and workspace, and food, and water, and housing, and electricity supply (-:), needed.