The difficulty in what you are suggesting, Raymond, is that the waypoints maintain the CRZ ALT, then you might see a waypoint with an Altitude Constraint, then the next waypoint display the CRZ ALT again. So you might wind up in a very shallow descent until you reach the airport, because it doesn't know where the T/D is. The T/D doesn't exist in the route, so can it know where it is? Still, it is definitely worth trying. I have not yet tried it, but it could turn out to be another "fix"!

The problem appears to be that the FMC does not know that at some point you want to reach RWY XXX at (lets say) 20 feet ASL, so even with Altitude Constraints in the latter part of the STAR, it still believes it has to fly at Cruise Altitude beyond the arrival airport (until END OF ROUTE is reached).

In my fix, I will try a waypoint to remove, then erase the change after anything from 10 seconds up to 60 seconds. If that fails, I try a different waypoint to delete, then erase the change. I can sometimes try doing that with ALL the waypoint in the STAR and TRANS!! Other times, I will remove the the altitude constraints that use the A (at or above) or B (at or below) until I get it to hold change and retain the T/D. In the end you can force it to accept the change. In the worst case scenario, I scrap the STAR and just select a runway to land on (i.e. 16, 34 etc.) without the ILS GPS or RNAV associated with the runway. I take note of the waypoints and any constraints in the STAR, and add them manually. In the end, I get my T/D on the route.

If you get impatient, do not expect to get a result. Having said that, if I get frustrated, I fly somewhere else where I get my T/D in the route. Or at worst, I change aircraft if I get p*ssed off enough with it. So that tells you that even I can lose it with the CS 767 (and the 757 which suffers the same problem). In truth, I get better results in the 767 than I do in the 757, so the 757 is worse for me, so I fly it a lot less.