Creating a plugin, or a file that Fusion 360 can import: suggestions?

[OceanHydroAU]

I've got years of research encapsulated in C and Perl programs I've written - it generates "ideal" turbines and propellers.  Output is my own custom spline text files, and/or RML-1 milling language commands.  I wrote it all from scratch.

For simplicity - assume that the output is a propellor shape - generated by draping a form over a set of 3D spline points (my own J-Spline points - not a normal spline).

I now want to adapt my code so that my work can be imported into Fusion 360; preferably without it being too hard for me to code.

Can someone suggest...

a) should I attempt to convert my code into a plugin for fusion to use?, or

b) should I find an output format that makes sense for my code, and modify my output to write it to something that fusion can read?

If (a) - what's the fastest way to learn and get that done?

If (b) - what's an easy file format (preferably text) that's able to support the concept of splines?

I'm guessing (b) will be easiest?: I found the below on these forums - will any of those suit:-

The following file types can be imported into Fusion 360:

• Autodesk Alias (*.wire)
• AutoCAD DWG Files (*.dwg)
• Autodesk Fusion 360 Archive Files (*.f3d)
• Autodesk Fusion 360 Toolpath Archive Files (*.cam360)
• Autodesk Inventor Files (*.ipt, *.iam)
• CATIA V5 Files (*.CATProduct, *.CATPart)
• DXF Files (*.dxf)
• FBX (*.fbx)
• IGES (*ige, *iges, *igs)
• NX (*prt)
• OBJ (*.obj)
• Parasolid Binary Files (*.x_b)
• Parasolid Text Files (*.x_t)
• Pro/ENGINEER and Creo Parametric Files (*.asm, *.prt)
• Pro/ENGINEER Granite Files (*.g)
• Pro/ENGINEER Neutral Files(*.neu)
• Rhino Files (*.3dm)
• SAT/SMT Files (*.sab, *.sat, *.smb, *.smt)
• SolidWorks Files (*.prt, *.asm, *.sldprt, *.sldasm)
• STEP Files (*.ste, *.step, *.stp)
• STL Files (*.stl)​
• SketchUp Files (*.skp)