I like the ray-poly idea, too.  But unless the memory leak can be plugged or avoided, I can only implement that by stepping outside of PoserPython or revising the whole concept to use the Set and WorldVertex approach.  Both possibilities, but this idea should be tested first since it doesn't require revising major elements in the existing code.

I'm fairly certain what I mention above is terribly incorrect.  I wish I were able to visualize things like this.  

In thinking about the "pattern recognition" problem of identifying certain features, I end up thinking about ways of dealing with mazes in game programming.  A path through a mesh would be a lot like a path through a 2D maze in a video game.  Could the A*algorithm or some fractal-derived method help?  No idea.  The math, again, is over my head....

===========================sigline======================================================

Cage can be an opinionated jerk who posts without thinking.  He apologizes for this.  He's honestly not trying to be a turkeyhead.

Cage had some freebies, compatible with Poser 11 and below.  His Python scripts were saved at archive.org, along with the rest of the Morphography site, where they were hosted.