thanks for posting this detailed question, it's a pretty interesting setup u're trying to achieve ))
for ur Microsoft solution, yes u can totally use azure database migration service (dms) for this one way replication! the latest version supports continuous sync from sql mi to another sql mi, even across subscriptions (same tenant tho). here's the official doc that confirms it works https://docs.microsoft.com/en-us/azure/dms/tutorial-sql-server-managed-instance-online. the cool part? ur custom tables on the target won't mess with replication since dms only syncs what u configure.
about ur 11 TB database - aha, that's chunky but dms can handle it. just make sure to pick premium tier for dms and monitor throughput. do a test run first with a smaller subset to catch any weirdness early.
now for stuff that works beyond just microsoft... u might wanna check if logical replication could work here too. some cross platform tools like debezium or even sql server's own change data capture (cdc) with custom etl might give u more control. worth looking into if u need to tweak the sync logic later.
also, this might help in other tools too - consider breaking ur big sync into smaller batches if u hit performance walls. sometimes doing it in chunks is smoother than one giant push.
while this setup is microsoft approved, remember that writes on ur third instance won't failover automatically. so if ur primary goes boom, u'll need manual steps to repoint stuff. not ideal but that's the tradeoff for custom writes ))
let me know if u hit any snags! microsoft's got ur back on this one, their docs are surprisingly clear for once https://docs.microsoft.com/en-us/azure/azure-sql/managed-instance/replication-between-two-instances-configure-tutorial happy replicating! :)
Best regards,
Alex
and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment