Gabe, you can create every output as you like using XSLT. I know that the current included XSL Style Sheets are difficult to adjust on your purposes. This is related to its generic nature - it should work with every definition of udt.
Writing custom Xsl Stylesheets is a lot easier task as you know your columns. There is no need for checking the fields definition if you know it.
Can you write your desired output in html? Writing xsl is not much more difficult if you know your schema.
Take as example "<strong>Steve Smith</strong><br>President". If we would have simple [TOKEN] language you would write
<strong>[NAME] [LASTNAME]</strong>
<br>[TITEL]
but now you need to deal with the udt and xsl:
<strong><xsl:value-of select="udt:Name" /> <xsl:value-of select="udt:LastName" /></strong>
<br><xsl:value-of select="udt:Titel" />
There are some more steps, but a final script looks like:
<xsl:stylesheet version='1.0' xmlns:xsl='http://www.w3.org/1999/XSL/Transform' xmlns:udt="DotNetNuke/UserDefinedTable">
<xsl:template match="/udt:UserDefinedTable">
<xsl:for-each select="udt:Data">
<strong><xsl:value-of select="udt:Name" /> <xsl:value-of select="udt:LastName" /></strong>
<br><xsl:value-of select="udt:Titel" />
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
UDT3.3.7 will come with an updated documentation and contains some more information you will need writing powerfull scripts.
PS: I like the idea of a public script repository