I don't know, it's the cheapest CAM software out there, not really too surprised when it can't do the most complex stuff for $500k+ machines. If you were to complain about turning tool definitions being painful or drawings still being a steaming turd and lacking truly basic functionality, then yes I'd agree.
We do actually program a Swiss machine on it currently, just posting out movement code and pasting into a two-path editor, but it's quite a lot of steps, a heavily modified post, and a lot of potential for human error. Esprit, Mastercam, Featurecam, Solidcam, NX etc all have multi-path options, and they all cost about as much as 20 years of Fusion subscriptions at current pricing. Our Tornos swiss machine has macros for part pickoff etc that asks you for part length, collet nose length, how far on to the part you want to grab, and then goes and does it all for you. It would be relatively easy to write yourself a macro that does the same things and requests all the necessary variables from you, calculates the necessary subspindle position and then goes and grabs the part. We just use the Nakamura-provided templates in Manual Guide-i on our other lathe for pickoff though. Hand-wheel the subspindle position in to where we want it, enter the value, and we're good. You could use ManualNC to do that, or modify your part handling (subspindle grab, partoff, subspindle return) using the Fusion commands.
It is pretty easy to use the Manual NC function in setups to write your wait codes into the CAM, without requiring any post mods. Click Setup --> ManualNC, select type as "pass through" (meaning whatever you type in there will get passed through to the output .nc file without being changed at all, so you can write something like "M901;" in the box and "M901;" will then get written into your output file verbatim - no quotation marks needed but end-of-blocks are), create a bunch of them from M100 to M120 (or however many wait codes you think you'll ever need at max), give each function the same name as its wait code (or something like Wait 1, Wait 2, etc) and then you can drag and drop them in between operations as required to have it insert the wait codes in the output.
There are some potential traps to be aware of with doing this, like if you put wait codes between two operations with the same tool, the post won't recognize anything you've written in the ManualNC window (it just copies & pastes it into the output file without reading it), so it won't necessarily retract or force a tool change or do any of the things you might typically expect it to do otherwise. Fusion also won't read/interpret anything you write in a ManualNC in any way as you're effectively hand-writing G-code), so when you run a simulation, it'll still just run everything in Setup 1 sequentially, then everything in Setup 2 sequentially. But if you're just trying to sync up a few things and you can model it in your head, it'll help.
