Honestly, the biggest issue I see with implementing this is the naming of the token properties and the code of the various frameworks out there. You would either have to code an import for each framework, or something similar, or the frameworks would all have to be rewritten using a standardized set of token properties . . .
Correct. So the "integration" is just the fact that it can create tokens based on images in the portfolio, link to the portfolio for quick updates, and extract and store the 3 statblocks. Since Hero Lab supports more than just Pathfinder, you obviously can't hard code a specific RPG.
But, I think you will find this integration is a lot easier than cut/pasting the data into the token. Also, a new macro that can grab data from XML using XPath makes it a better approach (IMO) than using regular expressions and also makes reading/changing the macro easier. I've supplied a macro in my campaign that does this. If your framework used different properties, you should be able to change it easy enough. Not every framework will want/need the same properties.
I had thought of adding a <link> property or such, basically just adding a place to add an xpath on the properties page but a lot of properties are really JSON objects or string properties so it's not a 1:1 mapping.
Now, of course, a framework may still want to use regular expression for non-hero lab users but it's here for use if you want it. I for one didn't want to do some sort of "export" in Hero Lab, copy, open MT, click macro, paste, "process" anymore for myself so here we are
Edit: BTW it's already done, you can view/test it in my fork...