I don’t like the argument that Epic isn’t implementing C# for anything more than defining build settings because they don’t like it. It’s just as valid to say that the people who are requesting C# be implemented want it because they do like it. Python is more widely used and understood by a far greater number of people across a wide range of disciplines, and it’s incredibly easy to implement, so why not Python? Honestly it just seems that people who have used C# just want to use it for everything, even if it’s not the best choice, it’s just familiar, therefore it’s “better”… Which isn’t true. I got my start in programming working with C and C++ and I would much rather work with those, not because of preference, but because they’re infinitely better for the task than a language like C#. I use C# for developing applications on Windows where I want to use the .NET Framework/Core, as doing a lot of things specific to the Windows OS is trivial that way, but for me that’s the only time I’m happy to work with C#.
I worked with Unity for several years before jumping to Unreal. I found it extremely refreshing to be able to work with C++ and directly work with the source of the entire engine. Basically, I can do whatever I want. A C# API that would allow you to do a fraction of the things you can natively do using C++ in Unreal would just not be feasible to create. And of course Epic’s sole ambition is not to convert Unity devs.