Some points-
- Compared to native, .net already has a gc and large standard library, So, porting should be easier. There are version of PHP(http://www.peachpie.io/) and Python(https://github.com/Microsoft/Pyjion) running on top of .net runtime.
- Just like Java, Kotlin will appeal to C# devs a lot, which may not be true for some other languages like C, C++ or Go.
- Native devs tend to not like runtime dependencies and gc.
- F# on .net is not a problem. JVM already had Scala.
- Kotlin already has Javascript as a target. So, Kotlin architecture is not JVM specific.
- Jetbrains is already on .net foundation.
- If you follow discussion on roslyn, the current open source C# compiler in Github, you will find C# is trying to be something like Kotlin. But maintaining backward compatibility is holding them back.
- Kotlin has a converter from Java. A similar C# to Kotlin converter will be very useful to attract C# devs. And Jetbrains already parse C# for Resharper. and this conversion will be idiomatic for C# devs, which is not true for other platform devs. C# devs could not even move to F# that easily.
- Jetbrains has Resharper with a large audience base. They can use it to push Kotlin. And a full featured IDE Rider is also on the way.
I see an unique opportunity for Kotlin in .net ecosystem. With it, it may become the ultimate garbage collected C-family language (Rust is the non-GC LLVM king), for every platform. In my simple knowledge I see more value in porting to .net than porting to LLVM/native for Kotlin. Please do it.