Isolating a Distributed Replay environment

I'm a little nervous replaying a captured trace/workload for performance analysis... I'm using an isolated service account to run the SQL Services, including the Distributed Replay controller & clients....Is that all that is needed to ensure replayed transactions won't jump across to the prod database? IE, is it possible that procedures or CLR objects could reach out and connect to another database, even though no linked servers are defined? TIA!