But what information would a tag output give you? I can't imagine it giving you any more than a point and string, which would be the exact same inputs that you gave to the tag component, so why can't you just use those?
In terms of fabrication labeling tags are really not of much help, other than visually what you see within the viewport. If you need text that has the potential to be fabricated/laser cut, then the text needs to be actual geometry, which the text tag doesn't create.
Ah, we run Dimension ULS lasers, which use printer interfaces to generate cutfiles. Text dots are printed, thus cut. Also, oriented text tags can be exploded post-bake into lines, which we've done. The problem we've had is maintaining explicit relationships between line segments in a cut, and their respective annotations while unrolling. We can do it by hand, but being able to do it within a GH script would be fantastic, as we're working on a project that might involve unrolling several hundred componens.
I concede, though, it is a low priority suggestion with a minuscule scope.
This still doesn't sound like the output of the text tag is the issue. If you're trying to retain label relationships during unrolling there's only a few ways that I know to take care of that. There are about two ways to take care of labeling surfaces in away that will "persist" after unrolling. The first, which is more manual, but is a little more straightforward, is to actually trim the label from the surface. The trims should be retained by the unrolling if properly selected and you'll have your curves. The second, which is much more viable, especially for large numbers of surfaces, is to set the name of the object before unrolling, then use that name to add a label (via script). There are GH scripts out there that will name objects while they are baked, and I'm sure there are scripts out there that will take the name of an object and either add text, text curves, or a text dot. Does that sound like it might help?