Edit: uh... the post is gone? There was a post by someone named Escain, stating interest in working on Path WB. But now is gone? Anyway, I'll leave my response here just in case.
Hello Escain, welcome to the big family. BTW, I am a quite new member myself. You can talk to the the Path developers at this
Here is a very brief introduction to Path WB from my perspective. You know that most of FreeCAD's CAD part is built on top of OpenCasCade (OCC), which is quite good in many aspect, especially for 3D modeling. But CAM also needs a lot of operations done in 2D space, which unfortunately, OCC is having trouble with. So, Path WB picks another library as the foundation, libarea from HeeksCNC, which in turn is based on the powerful 2D polygon processing library called ClipperLib. If you are also into 3D printing, then just about any open source slicer software out there is using ClipperLib too.
Before I came into the picture. Path mostly relies on Python to bridge between libarea to OCC and FC, for things like section 3D model and convert to wires that are readable by libarea, and then convert the output back to OCC wires for displaying and stuff. My contribution here, and also what this thread is all about, is the Path.Area python module, written in C++, which serves the purpose of bridging. The goal is to abstract libarea/ClipperLib's function from the rest of Path WB. Path.Area's code is at src/Mod/Path/Area.h/cpp, if you are curious. Right now, I am busy with something else, and is not actively developing Path.Area. You can talk to the other developers to see if you can help with the other aspects. I think your expertise in UI will certainly be helpful. I do intend to further develop Path.Area, or maybe extend it into another module, as a slicer for 3D printing. But that won't be in near future, I think. But if you are interested, let me know and I'll be glad to point you to the right direction.