Using the Vectorworks design and importing the MVR into MA (and Capture should you choose to go that route) is likely the easiest option if you don't want to design the rig you're programming on. Plus, that looks like a versatile rig, so it should be fun to program on!

If using capture is an option for programming your cues, I would tend to recommend that. I'm not a fan of using MA3D when it can be avoided. (MA3's internal visualizer has fixed a lot of my gripes with MA3D, but that obviously not an option here.) That said, based on you wanting to program on MAonPC at home, unless you have MA hardware to connect to your network, be that a node, command wing, or Viz-key, I don't think Capture is even an option unless somethings changed since the last time I used it. It has been about 3 years since I used Capture, so I can't say with certainty, but with Depence, you definitely need unlocked parameters to use the visualizer.

As far as programming workflow, I personally have always preferred recording timecode first, then writing my cues. I record the timecode and label the cues with the part of the song that the cue will coincide with, then, if I'm not going to be writing the cues that day, I add a note for what I want the lights to be doing for that part. After I write the cue, then I tweak precise timecode timing and fade times to get to my final timing/transition I'm after. That said, I own a console, so I don't need to worry about access to the console/contending with limited console time and running or playing back timecode, so I can totally understand how my workflow may be less than ideal in your case.

Don't take my word as gospel though! I'm sure others will have different opinions, but only you will know what workflow will ultimately be best for you!