The way double sided work in VCarve Pro is managed has some nice features (particularly the ability to virtually flip the material while seeing the vectors through the opposite side and being able to snap to them). But I just never liked working that way.
You can imagine the length of discussion this topic can have considering all of the variables, personal preferences, machine capabilities, production volume, reliance on coordinate zeroing, etc. (lol and that is just on the milling side of it). Now stack on to this a laser machine (which I find to be much easier to work with for double sided jobs in a few key ways).
There’s also a fundamental difference for me as to how jobs are run VCarve to Mill vs LightBurn to Laser (but I could manage this the same). That is, with VCarve and those toolpaths, the post processor output GCode is saved to a file and that file is then loaded into Mach3 to run the job. So for your double sided mill work, you are saving top side and bottom side files individually and then running those when appropriate (depending on how you manage your indexing process).
Mostly, I run jobs to the laser directly from Lightburn to the controller (not using a saved file). But you can 100% go the route of saving a job file for each side and having that run in the same way you may for VCarve mill work.
The only real difference between the two apps is that VCarve provides a UI simulating the flipping process. The similarities that remain are choosing how you want to manage the flip and how you index the material to the machine coordinates.