In reply to Vinay Jain:
The intent of the “input” monitor is to ensure that the driver has truly driven the input interface the right way (timing accurate). So, the input-side monitor, in essence, translates bus-level activity back to transactions, which are eventually forwarded to the scoreboard.
If you are still looking for a hack, where you want to bypass the input monitor altogether, please look at this post:
https://verificationacademy.com/forums/uvm/uvm-way-passing-information-monitor-sequence-agent