I don’t think it is a good idea to install a piece of software with both package managers.
Yeah. That’s why I asked if there was any overlap between what could be installed with the package managers. Dependency resolution is another factor to take into consideration. Even though a user may not intentionally install the same package with both systems. There is a decent possibility that they could end up with different versions of the same executables being pulled in as dependencies of other packages because one package manager doesn’t know what the other is doing. It can get even more confusing because the PATH variable may not be the same in all contexts (e.g. an application launched via a .desktop icon or from a systemd service may have a different PATH environment setting than one lauched from a terminal). So, for example, if someone runs something that depends on ffmpeg from the terminal, it may work or not work because it is finding the “Homebrew” version of ffmpeg. But if the same application is started from a systemd script, suddenly it behaves differently because it is finding a different ffmpeg binary. That sort of thing can cause quite a bit of confusion and frustration if the end user doesn’t know what is going on.
I’m sure that “advanced” users and developers that understand how these things work would have no problems dealing with such issues. But I’m not sure that it is a good idea to recommend such a system to the general end users who might encounter such problems and might not know how to resolve them.