Awesome work! Really exciting progress!
What about using OpenVDB as a bridge to render the SDFs?
The basic workflow would be to create SDFs, transfer them into OpenVDB format based on sparse volumetric grids, and then use GPU-based rendering techniques of OpenVDB or GhGL to render the OpenVDB field or to then generate the final output mesh.
Geometry could then be created through different means e.g. point clouds, SDFs, mesh, brep and combined using OpenVDB. The OpenVDB file can then be used to create one tight output mesh, perform simulations, or create slicing data for printing.
Have a look at this thread and comments 69 - 73:
As far as I know, there there is a render in Rhino/GH for GhGL but I have not seen a render engine in Rhino for OpenVDB files, which seems to be the missing piece.
Yes, there is Dendro for creating and editing OpenVDBs - but the problem is that for every change in the field (or any Dendro component in the Grasshopper workflow), Dendro needs to generate a mesh as an output to render the field inside Rhino. However, if there would be a direct render for OpenVDB, this would open up the possiblity to create super fast and robust workflows.
I am not an expert in computer graphics. It is just how I look at it as a user after building many design workflows with Grasshopper. 