Nothing has changed at the current time. Currently if the user has any prior ticket orders then the fields are pre-populated from the most recent order.
I think the only reasonable way we could support this is by convention of custom user profile property names. That is we can't map arbitrary custom property names to those field but would could look for user profile properties with specific names and then if found use those to pre-populate in the absence of a prior order.
So I'm thinking the conventions should be:
if user profile properties are found with those names we could use them. It might require updating existing properties in the database to match these conventions in some cases if other names have been used.
I'll log this request in our project tracker and see if we can get to it for the next update to Event Calendar Pro.