IIRC main Fedora used to not do this until some update crashed people’s sessions including the update process which left their install in an unbootable state.

The ostree based versions like Silverblue avoid this by their updates not touching the running system and instead creating a new folder structure with the updates applied that will be booted into on next boot.

I just use the Firefox flatpak from flathub.

Definitely a strange choice for a distro that pushes flatpak to not use it for the browser by default.

See https://wiki.winehq.org/FAQ#How_good_is_Wine_at_sandboxing_Windows_apps.3F from their FAQ

Are you referring to the ones with excessive sandbox permissions that flathub allows by default? Or is this something else?