Ghosting: by bind-mounting over the system fs -you might introduce a bug/condition that doesn't show up in a recovery boot scenario, or forensic analyzis of the filesystem/disk - you could introduce "ghost" files/artefacts.
Yes, sure. That doesn't stop hundreds of vendors with custom install scripts who will use /usr and /opt which is the current state of things. Systemd actually provides a workaround here which stops that package from changing those hierarchies globally, which... seems like something you'd want?
> you might introduce a bug/condition that doesn't show up in a recovery boot scenario
Why would you try to run anything but recovery tools in a recovery boot scenario?
> or forensic analyzis of the filesystem/disk
You can reproduce the same environment using the same overlay configuration - that setup is not hidden from you. It's not any more confusing in forensic than a docker service and we deal with them (including bind-mounts) just fine.
Honestly, it seems great and not very tricky for a system which already manages namespaces with private mounts.