> WSL2 is not (installed and) activated by default.
Windows also does not ship with ocicl (by default), but no one's gonna complain about that. If you'd like to install this piece of software on a Windows machine, think of enabling WSL2 as a preparatory step, like how you'd have to install MS Visual Studio / Cygwin to build Windows-only software, or install a DLL to run some Windows-only software.
> I wrote none of my Lisp tools on Linux, and I never received a Linux-related bug report for those.
Congrats. It is absolutely a good thing that you did not have to touch Linux in order to write software that (presumably) runs on Linux. Maybe the other OSes of the world can learn a thing or two about that.
And it is also good that you never received a Linux-related bug report. Presumably, your software runs flawlessly on Linux. Or, more likely, Linux users of your software know how to fix issues that may pop up and move on.
However, your limited experience of the world does not have to accurately portray how the world actually is.
> I wonder where I can find numbers on that.
The most popular implementation of CL is SBCL (ref: State of Common Lisp Survey 2020). SBCL is primarily developed and tested on Linux, and its largest industrial users also run it on Linux servers (same goes for ECL, Allegro, and LispWorks). This I know from being a (passive) participant in the CL community. I'm not sure I can get you numbers on this, but I can get you numbers that show SBCL receives bug reports for Windows far more than it does for Linux, despite Windows being one of the least tested or prioritised platform, so I'm not sure your method of judging a platform's importance is very good.