Does using Estlcam mean that I create the tool paths in Estlcam, save the gcode and than send it directly to Carbide Motion?
It does not support "direct send" like Carbide Create does to Carbide Motion. You'd instead save your CAM paths (created in Estlcam) in ".nc" files, then open and run in Carbide Motion
If I use Estlcam than I will not be using Carbide Create?
See above... only if you choose to not use Carbide Motion.
Ok a 3rd: Can I use Estlcam to fix the svg file, save that fixed svg file and than open it in CC?.
Negative... no SVG or DXF save/export.
I hope please that these are good questions, If the advice is to use Estlcam to fix broken paths in a svg file and than open the svg file in CC than I will dedicate a learning effort to Estlcam. Also I would like to maintain a concerted effort at using CC and CM. Thanks for understanding my rambling (for which I apologize). And of course now I'm the one that needs to be careful what I ask for.
No worries... I am using 2 tool chains (the Carbide Suite and CAD/Estlcam) also using 2 controllers (1 for GRBL, the other for Estlcam). I love everything about the prorgram, especially all the CAM strategies and operations it performs. I'm also running all my STL jobs using Estlcam. I wholly recommend this software if it fits the bill