I wouldn’t know to be honest- that’s a bit more under the hood info.
But generally speaking, if you’re working with a 3rd party effect that uses only Motion to be developed then it should be comparable in performance to a ‘built-in’ effect made from only Motion components. It’s when a 3rd party UI, rendering engine, etc. gets into the mix that the differences in coding begin to emerge more readily.
Also if you notice you have the ability within Motion to publish much more of the Motion interface to FCPX than most plugins actually do. I guess this is to avoid overcomplicating effects within FCPX.
Noah
FCPWORKS – FCPX Workflow
Call Box Training