Hi,
Yes, I see what you are trying to achieve now. And yes, you may worry about perfs too soon. The key here, is: are you dealing with 100th of them transform, or few? And while you are in deve, you may have only 2 or 3, but what's the real goal when your game will be done? cause refactoring could be a pain down the road. So it's always a dilemna, develop slow because you fear what's coming up down the road or deliver the product and then make it evolve. I prefer number 2, cause too much games and projects stays in the basement and never see the light because of the initial development time was too long.
Now, I think it will be good one day to get a FsmTransform, because I do agree, it's known that caching transforms is a good thing on mobile.
Your solution, if you want to go far with this, is to indeed use FsmObject of type transform, and recreate the related transforms actions to use a FsmObject as its target instead of a GameObject, and then you will have your caching system in place. It would not be too much work, as really you would copy paste the actions you are interested in on a per needed case and start building your custom actions folder as you go.
bye,
Jean