Actually despite the nintendo header it clearly isn't a nintendo file at all... look at the contents wtf. He has full control over the system.. no region control, a debugger in regular use (because he's added a lot of these libraries himself). All from breaking out of the boundaries with an xml exploit - i really think this is going to be the biggest thing in console software hacking for a while if it can be adapted, surely it can when it's proven to be effective already.
What i linked was more like a blog of what he was last doing.. unfortunately the best plan, ALLOW_DISCRUN_IN_SOFTLAUNCH.value = "0"; which is to allow a disc to run the xml exploit, clean out the system memory and reset with his CafeX custom firmware. Really with these actually in our hands available to us, Wii-U just took a massive step.. once control is taken, you won't need to pay for ODEs, you won't have to worry about updates cause hes already been working on doing that for himself at the same time.
If you have a method of sending commands to your Wii directly well firstly there's some libs to help in the SDK, and secondly then you might be able to play around with the xml method and see if you can launch something, but it seems dangerous to actually use any write commands without knowing exactly how much to try and run. I see dirs leftover in sdk of his work before where he was just running 30 xml's all from each other with the add-on feature, all of those having ALL languages and locales enabled and deliberately having bad streams/music files connected to the executable. Somehow it must have been blanking out system memory enough to be overwritten gradually..