It would be useful for authors to be able to obtain the path associated with text. This probably means exposing some sort of path object.
There's no point in rushing to add this API until we have good reason to. I'd at least wait until the old canvas backend is gone.
Canvas v5 added support for Path primitives (http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#path-objects) and there is addText and addPathByStrokingText on Path objects.
From the bug description, this is not what addText is doing. addText is drawing a text along a path, this bug is about an API to get the path associated with text.
Tobias says this is not a Shumway blocker. Assigning to Tobias as a point of contact.