One of the templates I put up is without using multiport by the way, I just set up the enviornment scaffolding for you to have 16 multis. That gives you 256 tracks feeding 16 VEP instances with 16 channels each. You can make it bigger pretty easily if you need it, but its just an easy template to get started if you want to use the environment approach to multi's
As I said on the other thread, it really comes down to what you can live with. If you don't need super huge templates and don't care about having many VEP instances, then that can eliminate multiport as an option. Another reason to use multiport would be if you need more than 16 articulations for any one instrument track from EWHollywood. You could, for example, use multiport, without using multis...still return single stereo feed representing just one virtual instrument, but using multiport to deal with more than 16 articulations. I don't think skiswitcher could cope with that, but I could be wrong.
Anyway, if you don't care about super big templates, then remove that as a cocern.
Next concern is how many VEP instances do you want to wade through? If you want less then 10, then you might still want to consider multiport. If you are ok with around 20...then you can easily accomplish it without multiport, but still using some kind of LPX multi approach. There are three ways to handle multis in LPX. Pick your poison. Another reason to use either multiport, or non-multiport-multis, is in order to be able to submix entire sections in VEP.
Lastly, if you can live without big templates, and you can live with 50, 100 or more VEP instances, and can live without submixing in VEP, then you could do the single instrument per VEP instance approach, no multis at all. There are definitely advantages, but you will be limited to 255 tracks, 500 channels of returning audio from VEP, 16 articulations per track and many VEP instances to wade through.
it just depends on which gotchas you can live with...
Here's a post I wrote a while back summarizing the pros/cons of different approaches to handling multis in LPX:
https://www.logicprohelp.com/forum/viewtopic.php?f=1&t=132635&p=697195&hilit=multi+bug#p697195
EDIT: Another factor for you to consider is using skiswitcher. I do not think it is multiport aware, so basically if you rely on that for articulation switching, then you need to forget multiport at all for now.