I fail to see how this is a client problem that can be solved with a forum upgrade? Surely this is just applying a SSL certificate to the server, there's a whole bunch of wildcard certs you can pick up and install for cheap.
Will login handlers be able to more easily control how users login? Such as in my Sign in through steam plugin when a user logs in in for the first time they are presented with a screen to enter their desired username and email, would we be able to replace that with a step that asks the user if they already have an account or if they wish to create a new one?
There is one already made :P http://community.invisionpower.com/files/file/5393-sign-in-through-steam/
My entire goal in programming/displaying to put the user first not myself. It's true they aren't needed, but they are useful to some. As a developer I find that the "Issue confirmations" is really helpful in determining if it's a one user thing, such as a browser cache issue, or affecting multiple users which decides it's priority to how fast it gets fixed and patch out. It also helps out the user to know they aren't the only one with this problem, or that they are the only one and might want to check over their configuration.
The only thing I can add to this is that It should be designed more for the end user and not really what suits/works for you. You rely upon end users submitting bugs, you need to make this as easily attractive to them as possible.
Emulate the look and feel of the old tracker in ip.content?