Mark,
I would agree about waiting for stability. For the moment, let's say that has been accomplished. Remember that this is only and assumption for the sake of argument.
Why would an ordinary SW user want to go 64 anytime soon?
Running a 64 bit application on a 64 bit machine with sufficient memory (say 8Gb) will allow certain features not to crash SW. In particular, if you have ever run the Patbench benchmark you will know you can run SW out of memory by creating large patterns in a part. IMHO this type of crash may be responsible for more than one unexpected crash in SW.
If you run PDMWorks locally, I think 64 bit will help as well if you have a large vault because PDMWorks keeps its database in memory.
64 Bit will probably also help PhotoWorks with it's insatiable appetite for memory. For Photoworks we are probably looking at dual/quad processor systems when we get renderings using the memory 64 bit can supply. So there will be quite an investment in hardware to take advantage of this.
CosmosWorks will definitely benefit from 64 bit and multiprocessing. Another case of large hardware investments. The same is true of CosmosMotion and FloWorks. The CAE side would definitely benefit.
The one thing I don't think 64 bit will do is to make SW run any faster in the area of regeneration. It might, but I am not holding my breath on this front. This is a performance issue that resides more in software than hardware.
Once upon a time SW did run on 64 bit. I remember testing TriStar Alpha systems with SW 96 and SW97. Back then the reason was to get performance and a gigabyte of Ram was unthinkable and unaffordable.