In that instance then i would go with Tim's suggestion only in the reverse. Make it read as a logical statement when read outloud. Bill (view user profile) doesn't make sense to me when I read it out loud.
From a profile link stand point we maybe looking at this in the wrong direction. The ticket referenced says there are 2 links on the page with the user's name that go to different places. The other option here is to work towards the consistency of your links wihtin the interface. Consider a policy that says when the user's name is linked it should be linked to their profile, if it is not linked to their profile it should have accesshide information that tells the user where they are going.
For instance a grade table I click on the user and go to the user's list of grade. This link would be <accesshide>View all of </accesshide>(student's name)<accesshide>'s grades.</accesshide>.
To me the answer is be consistent in where the links goes when text is used, and I would agree with Damyon that WCAG says to add accesshide if more information is required to tell the user where the link is sending them.