You're not wrong. I need to put more time in with F#. It feels so elegant when I use it, I just have a bad habit of defaulting back to C# when writing .NET code as that's what I know best.
that's F#s problem. C# is a good language, and while F# has some great things ( discriminated unions, computational expressions, pipline) that make for better ways to create software..... they aren't so much better that it justifies the learning curve to get good at F# compared to just writing things in C# ( unless of course you are a F# programmer and then you can't live without all your toys... ). Also, good luck hiring F# devs. My own experience at my company, I did a bunch of things in F#, but upskilling people just proved too much of a side track that I ended up rewriting all the F# in C#, and it was actually amazingly quick to rewrite in C# ( I didn't like the C# as much, but it's fine).