For example no high profile MS client product is written in C# using the dotNet Framework. All parts of Windows (kernel/user mode, shell), Office and various applications are coded in native C or C++ against the WinAPI. Visual Studio is mainly coded in C++ too, with some dotNet bindings. Some server products (outsourced to Microsoft India) use the dotNet Framework like SharePoint and Exchange.
It would show confidence in their WinRT API. WinAPI will be around for a long time and even WinRT-API is based on WinAPI/Win32 subsystem and COM.
Beside that, MS Word, Excel, Powerpoint never used the native Win32 UI controls. The applications were developed in the early nineties with a custom UI library. Therefore it's highly unlikely that the full Office applications will ever be ported to another UI library. MS Word uses e.g. WinAPI "fibers" API, a rarely used WinAPI functionality that got popular again in recent years with Lua "goroutine" and Go "goroutine". The applications are based on OLE (Object Linking and Embedding) and MDI UI. The ribbon is implemented as an owner-drawn "menu" that overdraws the menubar. There are lite versions of Word, Excel, Powerpoint for WinCE that were ported to several different platforms including iPad touch version.
Office 95 italic "Microsoft" in window title: http://upload.wikimedia.org/wikipedia/en/f/f5/Microsof_Offic...
Word 6.0 in Win3.1, it looked like an alien on Win95 with "-" (Win3) instead of "x" (Win95) in popup-windows: http://www.windows-nation.de/Office/Word6c.png
Word 97 running on NT 3.5 (looks like an UI alien with Win95 look&feel on Win3.1 shell): http://upload.wikimedia.org/wikipedia/en/3/3c/Microsoft_Offi...
Office XP - looked out of place in WinXP which got a new theme at last minute; later the Win8 theme was inspired by OfficeXP: http://upload.wikimedia.org/wikipedia/en/a/ae/OfficeXP_Win8....
They are including the ability to specify the UI used for the platforms rather than having it done by their framework. I can see why they need to do so to satisfy cautious developers. I hope they're not doing so because the framework will have unacceptable performance in the first release.