In other languages like Java, I can catch an exception that was thrown from another library or subroutine and throw a new exception of my own that describes at a higher level what failed but still includes the original exception.
Java code:

Note, the original exception object is passed into the constructor for the new error, so all those juicy details are not lost, but instead stored as the "cause" for my error. I am given the chance to generate a useful message that describes the context of the inner error without losing the original exception.
CFML doesn't allow me to do this and I am forced to cram the original message and stack trace into the detail of my new exception. <cfrethrow> doesn't help since it doesn't allow me to add my own message and stack trace.
Right now, the throw tag allows me to pass in an exception object, but it is mutually exclusive with the other parameters. I think the best solution might be to simply allow the exception to be passed into cfthrow alongside a new message, etc and it will become the nested "cause".
It would also be ideal if the "cause" would present itself the same way nested Java exceptions do so my code doesn't have to treat them differently. This would allow frameworks to easily display nested exceptions regardless of whether they came from Java or CF.
Note, I have put in this identical ticket for Adobe ColdFusion and would appreciate a consistent implementation
https://bugbase.adobe.com/index.cfm?event=bug&id=3842667