Vuo is pretty different at its core, using push instead of pull when it comes to the data flow. This might be the most important thing to grasp when switching. Getting out of the subcomp mentality is perhaps a bit challenging at first. Points and lists and the generation of these are also king when it comes to both create and manipulate stuff.
Are these pure copies of one main line, or should all the lines have different properties in addition to the basic rotation/translation?
You can use the combine nodes to create a collection of objects that you then can transform again via the transform nodes. Combining makes all the objects you combine children of the object so that the relation may seem clearer after spending some time with it. This can also be nested and/or copied with new transformations.
Replicate in Space
Here you can use the Copy 3D Object (TRS) in combination with Make Points Along Line (key ingredient) to easily replicate stuff however you'd like. If you right-click on the From/To ports you can reset to generic type, then change it to a 3D point to use less nodes. Make Points along Spline can also be used to create more complex patterns with a curved (or crazy) approach to the "replication" points.
Attaching a demo composition with a few ways to do stuff like this. You'll need my mm.points nodeset which is in the node gallery. Poke around and see if it makes sense!
I thought I had released a XYZ lerp thingy long time ago, but it seems that I haven't. If it's needed for V2 I'll probably include it then in the updated package (that probably will break old comps).
It won't blend/morph scenes, but it'll do the points at least. Singular nodes attached, but will probably not translate well into the future. Use at your own peril, and make a note of which comps you are using them with so that you can easily update it when/if necessary later.
Yup, by using the "Append Text" node, you can collect everything into a long string from different sources, and then use the "Split Text" node to separate it into a list of texts based on a separating character (":" for instance). That character may be added in the XML, or by using the "Append Text" node for other sources. "Split Text" might also be able to "ignore empty" iirc, cutting out the empties if there are any. I.e. if using : as separator, a :: text list entry will not be made I think, but a : : will as it contains a space which is a character in itself (looks empty but isn't technically).
To clarify the formatting a bit; when making a text layer it will apply the style formatting to the text and create an image (in a broad sense). Making a text (as in "Append Text) is only a string, so that won't have style info attached. So in the composition I attached previously you process a list of text (strings) into a list of layers (images). If you process a list of text by attaching or adding something to the text instead, you'd end up with a list of strings that wouldn't have any style info attached. That can again be processed into a list of layers though.
Use the Process List node to collect the text into a list. As a bonus, you'll get a tidier approach to the whole comp as well :)
This will depend on how you generate your text to begin with though as any open spaces in the list still will generate a split. I've included one possible option in the comp, but this will have to be adapted to your use case.