I have given up on using graphical ssh clients on Windows since Microsoft started including OpenSSH. I find the combination of ssh and Windows Terminal to be a much better one. Occasionally I do still use WinSCP instead of acp or sftp from the command line.
An advantage of doing so is use of the same keys in native Windows and WSL without having to convert them.
Sure, in a manner of speaking. You can set different profiles to automatically run a console application, so setting one to "ssh user@host" gives you a profile that starts a given SSH instantly in its own tab.
I've been doing that for over two years now and I wouldn't go back to PUTTY for anything. Especially since the latest OpenSSH for Windows supports Yubikeys; the version Microsoft provides officially is a bit too old for that but if you use Chocolatey or download from the OpenSSH for Windows Github area you get a version that absolutely does work well.
Color me surprised, this actually looks like a pretty good SSH client! I was one of those people who bought into Terminus when looking for a good SSH solution on Windows, and while it looked fine, it didn't offer a lot of unique or streamlined functionality. This, on the other hand, looks like the no-nonsense software I was looking for. Unfortunately I don't use Windows on my development machines anymore, but it certainly looks worth trying out.
Not a big fan of those "combined" swiss-army-knife clients. MobaXterm is another one. Using separate clients is better, so you can keep everything updated.
I haven't had to use windows in almost a decade, but when I did I would keep the cygwin binaries iny path. Or later on, the binaries from the windows version of git.
An advantage of doing so is use of the same keys in native Windows and WSL without having to convert them.