I'll ask for this point but I seems that's impossible.
I`d like to ask for some priority on this one, because the way it is using PTP on large project may lead to lot of extra unbillable extra work on larger projects, or suboptimal file structure with extra hassle when working manually with the code.
The delivery to customer, the final code and images should be structured well. It should also be easy to follow naming schemes from raw files to pano files and project file to PTP file and build with xml and file structure.
Like it is today its likely to end up with 2-3 different folder naming schemes. Its not possible to rebuild either by changing panorama file in editor. the only solution is to remove the file completely and import it again, and add all hotspots and other features once agin.
Customer do ask for changes and they expect minor things like a little reorganizing and changing of names to happen quick. With a 100-200 node project small changes will lead to sick amounts of extra work - unbillable. Or delivering with totally messy file structures, which should not be a feature of PTP, it should be defined as a logic design bug.
You are of course in feature freeze by now, but this one should be fixed with a solution before release of V2.