I find that what is needed depends on the task. Mostly, it’s about whether you need to switch views on information frequently. If you’re working in a maximally focused way you already have the right info, so you don’t have to make the view more diverse.
Two monitors can be really helpful if you’re in a situation where you need one view to always stay the same(e.g. reading one document while editing another) and the editing app is some fussy internal thing that always wants to be on the first window when started, but I also haven’t had that setup in quite a few years. Tiling can get you 80% of that if the screen is sufficiently large and the software cooperates.
When in Windows I stick to using the Win + arrow keys shortcuts to tile; in Linux I’ve used a few different WMs over the years but lately have been using Ubuntu defaults and basically working with it like Windows.
There is a lot of utility from not relying on screens and using a small gridded or ruled notebook with a spiral binding as the second screen. Mark it up with color multipens and sticky notes, and take it around in your jacket pocket or a belt bag.
Arch is always “latest and greatest” for every package, including the kernel. It lets you tinker, and it’s always up to date. However, a rolling release introduces more ways to break your system - things start conflicting under the hood in ways that you weren’t aware of, configurations that worked don’t any longer, etc.
This is in contrast to everything built on Debian, which Mint is one example of - Mint adds a bunch of conveniences on top, but the underlying “how it all fits together” is still Debian. What Debian does is to set a target for stable releases and ship a complete set of known-stable packages. This makes it great for set and forget uses, servers that you want to just work and such. And it was very important back in the 90’s when it was hard to get Internet connectivity. But it also means that it stays behind the curve with application software releases, by periods of months to a year+. And the original workaround to that is “just add this other package repository” which, like Arch, can eventually break your system by accident.
But neither disadvantage is as much of a problem now as it used to be. More of the software is relatively stable, and the stuff you need to have the absolute latest for, you can often find as a flatpak, snap, or appimage - formats that are more self-contained and don’t rely on the dependencies that you have installed, just “download and run.”
Most popular distros now are Arch or Debian flavored - same system, different veneer. Debian itself has become a better option for desktop in recent years just because of improvements to the installer.
I’ve been using Solus 4.4 lately, which has its own rolling-release package system. Less software, but the experience is tightly designed for desktop, and doesn’t push me to open terminals to do things like the more classical Unix designs that guide Arch and Debian. The problem both of those face as desktops is that they assume up-front that you may only have a terminal, so the “correct way” of doing everything tends to start and end with the terminal, and the desktop is kind of glued on and works for some things but not others.