Yes, TLS clients send SNI and tools that don't send SNI are expected to not work (e.g. python older than 2.7.8), because many sites only work with SNI.
For example, any use of CDN requires SNI (unless you pay for a dedicated IPv4 address for your domain at the CDN provider, which is very expensive).
Many sites that actually do have dedicated IPv4 address(es) are configured to drop non-SNI connections or serve dummy certificates for non-SNI connections.
So you can just declare that your site requires SNI and it will be fine (unless you must maintain compatibility with clients so old they are almost definitely insecure and shouldn't be used).
One thing you should know is a quirk with HTTP/2 request multiplexing and TLS certificates that cover multiple domains. If a browser needs to perform a request to foo.com and opens a connection to your server and gets a certificate with both foo.com and bar.com in SAN, and soon after the same browser needs to perform a request to bar.com and DNS says it's the same IP address, since the certificate covers bar.com too, it will consider the already open connection to foo.com to be suitable and just multiplex the request for bar.com in that single HTTP/2 connection. If your backend "knows" that requests for bar.com cannot come to this server because connections with bar.com in SNI are handed to another server, you'll have a bug.