The argument I presented in that thread against SetPrimaryPartCFrame isn’t subjective and therefore not something you can agree or disagree with. Because of floating point imprecisions, SetPrimaryPartCFrame tears models apart. It shouldn’t be used unless you are not using it frequently (e.g. one or a few times). If you need something like SetPrimaryPartCFrame, write a custom implementation that offsets related parts in object space to a point of reference.
I’m not sure what synchronisation issues you’re referring to when you’re talking about tweens, but that typically doesn’t happen. If you’re talking about position desynchronisation, you can always account for that yourself with your own methods. Server-side tweening will be slow but synchronised and client-side tweening will be fastest but dependent on the client’s machine for its smoothness and such.
Synchronisation isn’t really a talking point here because both tweening and CFraming will both have the same implications. Tweening just defines end properties to be lerped through over a period of time while CFraming sets the item instantly. You want the better option, which isn’t SetPrimaryPartCFrame.
Also no, 0.01 as an increment for either SetPrimaryPartCFrame or while wait do look equally bad. Wait has a minimum waiting time of ~0.03 seconds meaning any value lower doesn’t do anything except set the interval to the minimum time and SetPrimaryPartCFrame’s floating point imprecisions are present regardless of the increment you use. While wait do is bad.