Honestly, as a user of both SolidWorks and Rhino, you would need to think very carefully before ditching SolidWorks and moving all over to Rhino.
Rhino is a great tool and sure you can create virtually any shape (in very skilled hands)m and you can draft...but...if I was used to SolidWorks drafting and modelling tools and forced to drop it for Rhino I would seriously doubt the sanity of my boss.
You mention that the tree fails in SolidWorks? That you want no history? You can do that in SW already. Just use freeze, or export as a parasolid and import the dumb part. We can argue all day about modelling in this app or that app but in our business we use Rhino with TSplines for concept work, take these to SW for final surfacing and parts...and drafting.
Drafting in Rhino is, well...if you want to go back 20 years, lose all manner of automated drafting tools, e drawings, associative (that works) drawing views, reliable sectioning, call outs, hole tables, etc etc.
Keep SolidWorks. Use it in tandem with Rhino. It actually partners up well. Someone suggested PowerSurfacing for SolidWorks. We have it but stopped using it as it was buggy, slow and unreliable compared to Rhinowith TSplines. I see use continuing to use v5 for some time until McNeel implement a native sub d workflow to match T Splines (either that or we switch to Fusion360 for this kind of work).