Please try the attached test-badpath.cfm
In the first 2 cases, output from Lucee is the same as ACF (cfmodule, createobject)
In the last one, if a CFC (see attached testComp.cfc) extends a cfc that does not exist.. (for example, someone put a bad cf mapping in path)
In Lucee, all the nested cfsavecontent will be impacted, but in ACF it is still showing the expected result.
I've added test case for this ticket & confirmed the issue happened on lucee. In cfsavecontent tag, If we create object with cfc having extends a another invalid cfc, doesn't throw any error in tcatch block. If we remove the try catch block, it working as expected.