TransactionValidation.fs does not need to verify the 'bounds' of a contract?

[pw96pw96pw96]

According the zen protocol's white paper, contract 'bounds' represents the amount of computation needed to run the F* program. If a miner receives a transaction containing a contract which declares a very small number for bounds, but in fact has a very large number for bounds, the miner will be tricked to prioritize such a transaction (if the transaction validation does not validate the bounds)???