MikeJ: As I understand the process, bagginsbill uses a Python script that creates the eye geometry and saves it into an .obj file. A variation of the script (or a call with different parameters, whichever happens to be the case) generates a variation of the geometry like, say, one with a wider pupil. This is also saved as an .obj file, which can then be loaded into Poser as a morph target.
The point is, it doesn't matter how many vertices the eye object has because the geometry for the morph is created by the script, which stoically computes as many or as few of them as necessary. No manual vertex pushing is required.
 

-- I'm not mad at you, just Westphalian.