Not re-using addresses makes sense, both from a security and potential privacy point of view.
I see #3 on the Bitcoin 400 Rich List has revealed their public key to the world. I take comfort in knowing that this owner would likely become a target first before any of my modest holdings, in the event of an ECDSA crisis. The blockchain could potentially be salvaged under such a scenario, but some coins could be moved without the owner's consent. I understand that not re-using addresses protects coins further by benefiting from the cryptographic hash functions, limiting any potential attacks.
Whilst I don't understand all of the cryptographic axioms and low-level fundamentals of pubic key and hash functions, I do understand their principles and appreciate the mathematics. Mathematics and its proofs are the only thing that my logical brain can completely put its faith and trust in.
However, at times I also have this silly illogical action-outcome monkey brain which tells me I would feel better if I see my keys signing a tx first before I send larger holdings to it. In fact, early on before I understood "change" (and did not consider coin control), I was rather ignorant to the fact that change was being spent to new addresses. Ignorance truly is bliss.
I now like to know the locations of my coins. However, I also don't completely trust myself manipulating the protocol specification (especially not raw txs) and still like to see some burden of proof. I also like using the reference client. I find myself exporting signed txs first before I broadcast, so I know where my change will be spent to!
For these silly paranoid moments, can signing a message and then verifying the message suffice as "proof" that the reference client and network will "accept" future transactions? Whilst I understand the signature functions are practically the same, I am theorising if some unknown bug in the larger majority install base could reject a spend from some weird malformed address. I recall an early version of bitaddress.org had some sort of malformed key issue. Wouldn't want to be in a position where the network would accept a spend to a hashed public key, but prevented its spend.
tldr. Paranoid.