That is absolutely possible.
For both Apache and nginx, you can define TLS options per virtual-host.
Taking nginx as an example, every block like the following (taken from Mozilla's TLS config generator can specify its own TLS options and preferences:
listen 443 ssl http2;
listen [::]:443 ssl http2;
# certs sent to the client in SERVER HELLO are concatenated in ssl_certificate
# modern configuration. tweak to your needs.
# HSTS (ngx_http_headers_module is required) (15768000 seconds = 6 months)
add_header Strict-Transport-Security max-age=15768000;
# OCSP Stapling ---
# fetch OCSP records from URL in ssl_certificate and cache them
## verify chain of trust of OCSP response using Root CA and Intermediate certs
resolver <IP DNS resolver>;
You can use any (hopefully valid) cert within the block, including re-using a cert between subdomains.
The TLS settings are distinct from the details of the certificate and key used.
However, although you can do this, it may make sense to consider, at least, using different certificates - it would allow you to revoke certificates for different parts of your site in case of compromise.
Using the wildcard cert, if that key is compromised, your whole site will be offline until you can get a new cert.
If you have per domain certs, and possibly a wildcard as a fallback, you make yourself better able to deal with that situation without necessarily affecting your entire service.