there are only like 2-3 ways to get it not activated on boot..
This is a misconfig of some sort, not random breakage (unless it is metad).
cat /proc/cmdline
disable/mask lvm2-lvmetad if your fedora version has it, it causes weird lvm issues (ie random fail to find/enable vgs).
Did "vgchange -ay" activate it and/or did you have to add the vgname on the line?
There are some volume_list options in /etc/lvm/lvm.conf file that people sometimes use that will use odd behavior.
I won't touch btrfs/zfs, I have had too many first person horror stories in the last 3 years to trust either with my data.
The risks associated with using btrfs/zfs depend on your use case, but so does your
expertise in configuring and maintaining a filesystem.
Many IT groups and users just reinstall the OS and fetch data from cloud storage
when user workstations have filesystem problems.
A lot has happened to many linux desktop users in the last 3 years. Technologies
moved on, and COVID-19 has many people wanting the flexibility of a laptop. Ubuntu 20.04 made
zfs the default, Fedora 34 made btrf the default. Distros need good reasons for changing the
filesystem. SSD's have replaced platters, people are using clouds for offsite storage, and more
bigger data makes bitrot more of a concern. File compression with btrfs is claimed
to significantly extend the life of SSD's (but copy-on-write increases wear). Laptops
replacing desktops increases the importance of encryption and makes a UPS redundant
if your external storage is in some cloud.