Whether a program can be compiled statically is a factor in whether I choose to use it. That effectively screens out many large programs that have numerous dependencies because compiling them statically often becomes too much hassle and the binaries are too large. For example, I compiled dnsdist statically using musl. Of course, "large" is subjective. I consider an 11M C program to be large but some HN commenters using memory-safe languages might think 11M is nothing.
1. Some have dependencies other than libc.
If "you" means me, then no, because I do not have the patience nor do I think it would be worth the trouble.
The binary would be enormous.
One thing I used to do many years ago is create compressed images of directories containing programs or files needed by those programs, e.g., /usr/pkg/bin, etc., using makefs and vndcompress, then save these to bootable USB stick. For example, I might install Firefox, then create the images. The way I use NetBSD is that I boot into RAM from USB. I may or may not use a disk. Writeable directories are mounted as tmpfs. I use RAM as disk. This is one reason I like small programs. Installing Firefox would take up too much space, i.e., RAM, so I would mount the USB stick after boot, then mount the compressed images over certain directories, e.g., /usr/pkg/bin. As I recall, this worked, but eventually I gave up on graphical browsers, as well as X11.