You can't use host  headers with SSL sites.

That's not entirely true. You cannot set these in the IIS UI for Windows
Server 2003, but as long as you are using Windows Server 2003 SP1 and above and
a wildcard SSL cert they can be set via script in the IIS metabase. See
www.microsoft.com/.../596b9\
108-b1a7-494d-885d-f8941b07554c.mspx?mfr=true for the steps for Windows Server
2003/IIS6. This can be done directly in the IIS Manager UI for IIS7. Afterward
you will need to add the necessary Alternate Access Mapping(s) for the https://
url(s) manually in Central Administration.

I have also found that you can
use host  headers by script but I was not sure of the order of operations. I
have already setup  static IPs for each site in DNS and on the web  server. If
you can do SSL with host headers, is there still a need for these static IPs?
The article didn't mention anything about them so I am curious.

A heavy emphasis on DMZ experience. DMZ (Short for demilitarized zone, a
computer or small subnetwork that sits between a trusted internal  network, How
does DMZ fit into a Sharepoint Engineers role?

From this perspective SharePoint can be considered similar to another web-based
applications. There are situations where you will want to deploy SharePoint in
a DMZ. Since it generally involves SQL server  and Active Directory as well, the
general security topics of hardening, server placement relative to firewalls,
ports allowed, etc. all apply.

You can do multiple SSL sites  on the same machine with either multiple IP
addresses or host  headers - there's no need to do both.