OK. document Converters are the standard way to do what you want, and can be manipulated through the Sharepoint API. That SPFile.Convert method you saw was indeed related to Document Converters. However, it in itself can't be used to do the conversion programmatically. There are three overloads (from memory!) on the PublishingPageCollection.Add method, and you use one of those to specify your SPFile instance, a GUID that identifies the document converter (find that in the Doc Converter Feature element file), then there's a priority indicator and you can plug in a config XML file too.
That's the document converter way, which would be the standard way. However there are commercial components that do such conversions too. There's nothing to stop you getting one of those, deploying it to the GAC with your feature and calling it's conversion methods from your event. You not bound to only using Document Converters to achieve this.
Now, I realise I've rambled a bit here! Am I making sense!?