Arch's primary package set contains the standard set - which I assume is similar to NixOS - but all of packages requiring tricky/custom configuration tend to be in AUR. Which has saved me on a number of occasions from having to follow pages of tutorials that you'd normally have to follow in order to install things when using Linux for a desktop.
For example, setting up nice fonts with great default settings in Arch is a single AUR package away.
good news is that it will be some 4 years until i have DRM on firefox... i mean iceweasel.
ps: while googling for it, I discovered https://wiki.archlinux.org/index.php/Arch_Rollback_Machine
I switched to KaOS (because they used pacman), but their install image fails to install before creating users and installing grub, so I'm back to a Gentoo LiveUSB, which doesn't fail.
Every time I leave gentoo, I'm eventually forced back. maybe Nix will be better.
A main practical issue is that Nix packages are often built with all possible options vs Arch minimal packaging philosophy. In practice you install something as innocent as mutt, and python comes as a dependency!
This is just an example that some of their packaging policies are a bit odd, but they are working on this. Imagine using Nix on an embedded device. All those extra dependencies might make a difference in terms of resources used.
That still doesn't explain why installing python is such a big deal for you, or why your desire to not install python is stronger than your desire to install mutt.
I'm not even sure what you mean by "your version of python is now tied to your email client and can't be upgraded separately". As long as the deps for each package are satisfied, either one can be upgraded.