Sim; para um determinado endereço IP do ouvinte / porta de combinação, cert e SNI e lógica de host virtual baseada em nome são distintas de outros ouvintes
Então, digamos que você queira que 192.0.2.50
seja SNI, com 192.0.2.51
e 192.0.2.52
como IPs dedicados:
NameVirtualHost 192.0.2.50:443
<VirtualHost 192.0.2.50:443>
ServerName snisiteone.example.com
# SSL directives here for this site's certificate to be served via SNI
# Note that this cert, the first configured, will be used as default
# for clients that don't support SNI
</VirualHost>
<VirtualHost 192.0.2.50:443>
ServerName snisitetwo.example.com
# SSL directives here for this site's certificate to be served via SNI - different cert!
</VirualHost>
<VirtualHost 192.0.2.51:443>
ServerName dedicatedsite.example.com
# SSL directives here for this site's certificate
# Dedicated IP, so this'll be the only cert on this listener, SNI not used
</VirualHost>
<VirtualHost 192.0.2.52:443>
ServerName dedicatedsitetwo.example.com
# SSL directives here for this site's certificate
# Dedicated IP, so this'll be the only cert on this listener, SNI not used
</VirualHost>