No, by design.
Script evaluation gives an unconditional boolean output: valid or invalid. If script validation could depend on context, that would mean script validity would need to be re-evaluated any time that context changes, complicating reasoning about mempool transactions, the meaning of confirmations, as well just generally causing significant CPU cost to nodes that keep unconfirmed transactions around.
Note that neither OP_CHECKLOCKTIMEVERIFY or OP_CHECKSEQUENCEVERIFY actually let scripts depend on height/time information; they only depend on the locktime/height that’s in the transaction itself. Validation of those locktime fields happens outside of script, which does mean that while transaction validity isn’t entirely context-free (it can’t be, because double-spending!), script validation never needs to be rerun.
