I haven’t used the sample so far.
But from the diagram, it looks like that the sample creates a SSL configuration (ArSslCfgCreate) before opening (ArSslOpen) and using the config when sending the mail, and this config is deleted after the mail is sent (ArSslCfgDelete).
I think that if you don’t delete this SSL configuration at the the end (leaving out the step ArSslCfgDelete) , you can re-use it later on (after it was created once) for sending mails by starting the sequence directly with the step ArSslOpen.
As I haven’t checked the source code, maybe there has to be done something more, but keeping the once created SSL configuration and re-using it should be possible (as it’s more or less the same then using a Automation Studio preconfigured SSL configuration in runtime).