Despite the equivocation, even that article notes that the problems exist primarily for the
Windows API compatibility implementations, not so much the basic (ECMA-standardised, however
useful that might be) .NET platform. When writing a GNOME/Mono/C# application, you don't need
to use any of that stuff.
Given that other distributions have been comfortable enough to ship those pieces (for use with
a small number of GNOME/Mono/C# applications, only one of which is actually included with the
GNOME releases), and for OIN to include it among the software components it will protect, it
seems odd to focus on GNOME as a vector for Mono.
There is certainly no strategic adoption of Mono within the GNOME project (nor, it should be
pointed out, has there been of Java before or since it became usefully Free Software).
I'm not sure your blame attribution is correctly targeted. :-)