That’s not true in incus: new features are quite aggressively back-ported to the LTS branch. I have not been bitten by it in the past, but I’d say it is a risk.
Another thing to beware of is that the zabbly packages between point releases (e.g. 1:7.0.2-ubuntu26.04-202610301448) have no corresponding git tags in the main source tree. AFAIK it’s handled via cherry-picking patches in the zabbly/incus repo, but that’s not tagged either.
However, as long as there are no changes to the database schema, it’s safe to roll back. I presume this is why the OCI container functionality was not back-ported to 6.0 LTS.
It’s really just VMs. In theory, live migration of containers is possible with CRIU, but it has so many limitations and caveats (e.g. your container cannot have a network interface!) that in real scenarios it never works.
However, incus 7.0.2 has recently back-ported the feature for “near-live” migration, where it will repeatedly send incremental storage updates until just before the actual cutover, for a very short off/on cycle. And that should work between independent nodes with no shared storage. I’ve used this approach manually in the past, using incus copy --refresh multiple times followed by a stop on the source, a final refresh, then a start on the destination
As for VMs: I have never tried live migration without shared storage, nor between independent nodes, but I don’t see any documented limitation which says this shouldn’t work.