ID 494734 - lx.result and lx.excResult does not work as expected.

Problem summary
lx.result and lx.excResult does not work as expected. 
Customer reported version
modo.15.0v1
Customer reported platform
windows10
Steps to reproduce
1) Open Modo and select Layout > Palettes > Scripting.
2) Run the following script:

try: # Try running a render, then quickly abort the operation.
     lx.eval("render")
 except RuntimeError as e:
     # Reading the Commands log, and you'll see the command was aborted.
     result = lx.excResult(e)
     # But getting the result code from the exception, and it's always lx.result.FAILED
     assert result == lx.result.ABORT, "{} does not match the result code for lx.result.ABORT".format(result)

3) When the render starts, quickly abort the operation and notice the results. 

Expected behaviour
lx.excResult should parse exceptions and match them to the correct lx.result code.

Actual behaviour
For errors lx.excResult will always return lx.result.FAILED. lx.lastResult will always return lx.result.OK no matter what exception the command raised.

Workaround
Unknown.

Reproduced by support
This bug has been reproduced in:
15.2v1 - Windows 10
15.1v1 - Windows 10
15.0v1 - Windows 10
14.2v1 - Windows 10
14.1v1 - Windows 10
14.0v1 - Windows 10
13.0v1 - Windows 10
12.2v2 - Windows 10
Earliest version tested
12.2v2 - This issue appears to be in all versions of the product.