I tried this approach in the V1.8 beta (highly recommended!), and was not able to replicate a NO APPR condition using standard procedures. There may be an inconsistency with the earlier implementation of the terminal area approach logic.
However, a couple of tips when using Collins Pro Line avionics that are different from Boeing or Airbus:
When performing an ILS (or LOC) approach, coming from FMS navigation, it is advised not to arm approach (APPR) before being inbound to the glideslope intercept point (or FAF when on a LOC approach), and established on the final approach course. In the case of ILS Z 08 at BUR, that's the point roughly 2nm before BUDDE (or BUDDE itself for LOC). One can arrive at this point using LNAV/VPATH (or VVS if desired). This is especially important at some airports with multiple step-downs on the intermediate approach segment, and there's an outside air temperature that can cause altimetry errors sufficient for the glideslope to be below these constraints.
If on vectors from ATC (or self-vectoring) using heading select (HDG), then one should limit one's intercept angle to the localizer to ~30 degrees, and not to arm approach when too far laterally from the localizer as otherwise a false beam capture may occur.
Hope that helps.