As always with these things it's a matter of testing your show set up with representative content, and then pushing it quite a bit further to know you have a reasonable performance safety margin, assessing the results by eye. A test video with rotating bar and burnt in timecode with frames is useful for assessing video performance visually.
You can attempt to quantify comparative tests using the fps logs in level 3 logs in the Console, or CPU in the activity monitor, but neither is likely to give a true meaningful result (Particularly CPU) , that is applicable to all systems.. If you try this with level 3 logs remember to turn logging off again after.
I think it would be fair to say though that this order of efficiency with a rough score out of 100, with 100 being the score achieved by a video playing straight to a single surface., is reasonably accurate. (Starred scores are for methods that would be applicable to what you want to do)
Single Video direct to surface. SCORE 100 (for reference)
Single Video to 1 surface with 2 mirrored displays SCORE 92 (although this option would not allow you to mask one display)
Single Video looped back through Camera Cue to surface SCORE 85 (for reference)
Single Video looped back through camera cues to 2 surfaces SCORE 76* (Best Option for your applicaition)
2 Videos direct to 2 surfaces SCORE 56*
Where the syphon loopback really comes into its own is when you want very large numbers of surfaces with the same content (or different areas of the same source content)
Single Video looped back to 16 camera cues to 16 surfaces. SCORE 45 (CPU Disk and Memory still coasting along)
16 videos to 16 surfaces SCORE 1 (Unusable, everything pretty much grinding to a halt.)
Mic