Yes. It’s the same reason AppImage could work — if the licensing allows for the all libraries to be included in the image, because the Linux syscall interface is generally stable.

“We do not break userspace”

AppImages have a few problems. Ever seen how much dependencies you need installed to execute an AppImage?

You also need to be in an environment where you can create FUSE filesystems. And iirc the reference implementation requires the deprecates fuse2 library to work.

Snaps, Flatpaks, AppImages and static linking are all solutions to a real problem. But I don't think AppImages are an especially good solution.

I talked a bit with Richard Brown about supporting AppImages in Aeon, the OpenSUSE immutable distro. But he believed the base system would need far too much dependencies specifically to support the AppImage runtime including deprecated fuse2 support.

Snaps and Flatpaks have many more dependencies than AppImage, they are just not deprecated YET.

True, but I believe Flatpaks offer more than just "single executable applications". In the case of Aeon it's the primary way of installing additional software.