My remark had to do more with being stuck in a v3.5 world, thus making Unity devs live in an universe quite different than what everyone else is using in terms of APIs and language features, on top of Unity specific behaviors like those magical methods called by the component framework.
The new HPC#/Burst indeed are subsets of C#, but that's a very recent development, and completely unrelated to "Unity had to make their own C# dialect to avoid Novell/Xamarin licensing issues".
> As for Mono being already in 1.0, OS X only version, I am unsure about it, but the old blog was taken down
I have worked at Unity since 2006. Yes Unity was Mac only at that point, but it still used Mono there.