> One is lagging support in Visual Studio
I use VS Code, both for Python and now for F#, and so far my experience has been positive. But that might be because I've used F# only for very basic stuff, and I don't know how better it could be in some other language and/or IDE.
> scripts
I think I'll stick with Python for that :) But I'm thinking about maybe transferring some machine learning stuff from Python to F# in (some distant) future.
If you are used to python, and think that VS Code is very nice, you'll be blown away by the tools and functionality that proper VS offers.
>What are the F#'s downsides which prevent its more widespread usage?
The two biggest downsides I've encountered are not related to the language itself. One is lagging support in Visual Studio (didn't support folders for long time, poor cross-language C#/F# navigation, no support in .NET Core projects etc.) and the other is the lack of examples/frameworks for WPF applications when I needed them.
Other than that it's my favorite language for all kinds of tasks -- from production apps to scripts.