I'm not sure you can do that, because the contact selector requires the activex control to be activated and requires the Context.XML file to be added to the resource files. You may be able to use the template part and then go add the context file, but I'm not sure.
As for your original problem, if that username resolves in Outlook but is not working in the email generated by your form/workflow even though the name is resolved in the contact selector, then it again points me to that errant pipe in your example. I'm not sure why you think that's not a problem when it shouldn't be showing up and could easily be associated with the domain name due to being adjacent. Am I just seeing things?