You could then send those geometries to Revit using ImportInstance.ByGeometries. There is also a Springs node that lets you create Family Instances from geometry, Springs.FamilyInstance.ByGeometry though I haven’t used that so I can’t tell you exactly how it works.
I’m not sure if it’s possible to arbitrarily rotate Family Instances except maybe with Python (which I’m not familiar enough with). The only way I can think of is a two-stage process; first creating the surfaces to put them on, sending those to Revit, then getting those surfaces to place the instances on (FamilyInstance.ByFace or so), then getting rid of the surfaces again (requires a Python script; I should have that somewhere if you need it).
Archilab has a node that lets you rotate families by around an arbitrary axis but it’ll rotate them every time the script is run, cumulatively, so be careful with that…
I would switch to a simple, line based adaptive component family. Note that you could nest your other standard family into that one. This way you’ll actually save yourself HOURS of time, and avoid some issues the 'rotate family along non-world canonical axis can cause. This type of rotation is actually one of the reasons adaptive components came into existence, and an example of when you’re better off just doing what Revit wants you to.