There are a variety of actions you may take on a server that are prohibited in the documentation. I've dealt with several over the years in a VLDB world such as stacking multiple Crypto Providers, rotating TDE keys during a backup, and various DBCC stunts for compliance sanitation. These actions are permitted on the server and tests can perform these actions to completion without error or corruption. In all of those cases, I could run many valid error-free tests, but here's the kicker: Tests are not reality. Those cases also had the occasional error that was a SQL bug (rotating a TDE key during a database or log backup would crash the database and take it offline about 1% of the time, etc.).
Prohibitions show up in documentation after another SQL Server customer encounters a bug that affects uptime or corrupts data. Doc changes are much faster and easier than code changes, so changes show up there first.
If it's important to you, then reach out to Support and get a firm answer that you are supported. It may simply be that certain configurations are dangerous, but a safe path is available that solves your problems. Unless you really love picking apart busted replication to try and recover all the data and getting it working again, I would assume there is a downstream impact my test didn't find and plot another path using supported methods.