My opinion:
Only build TweenMax on top op GoASAP if the drawbacks are negligable.
So at least not at this moment.
It might be a good idea to identify the factors that would slow down TweenMax and contact Moses Gunesch about these to maybe come to a solution that would satisfy both parties.
Ofcourse it would always be a good idea to have both a GoASAP and a non-GoASAP version of the classes so the developer can decide for his-/herself which version to use.