I wanted to circle back. We were never able to get the code from above working. However, we didn't try too long as we stumbled across a very weird workaround. The workaround makes no sense but I'd be curious if others experienced the same results.
We use the regular date token as shown below, not the email script token.
Hi {{lead.First Name:default=}},
This is the enablement date: {{company.Enablement Date:default=Date}}
Here is where it gets weird......
When we drop the email into a Request Campaign campaign to send the email, the Enablement date merges in the way we want it (Mar 20, 2014). However, if the same email is sent via a batch campaign, the email merges in that field in the 2014-20-03 format.
So instead of sending the email via a a batch, we set up another campaign to grab the members. We then request a second campaign that contains Send Email in the flow.
The only reason why we stumbled on this is we were originally using the advanced wait token as part of a Request Campaign campaign.