Yes and no.
Yes you can detect browser versions pretty easily. It is part of the headers send with each request. Matching them up with capabilities is somewhat trickier as is keeping such a list up to date.
No in the sense that your web/application server still need to allow HTTPS access using insecure versions of the SSL protocol and will still support low quality cipher suites. The SSL negotiation is already finished before you can detect the browser version and present the old.html page.
I'm not sure but I assume it is not unlikely that browsers will negiatiotate with an HTTPS server to use the most secure algorith, but it's possible for browser and server to mutually agree on the lowest, most insecure protocol they have in common as well as that will likely also be the most inexpensive computationally ; a valid choice for low power devices.
So even determining the actual cipher suite used may not be accurate in determining that the browser is "old".