I agree with that. While restoring the transaction logs to the secondary server, the users will be disconnected from the secondary database. Although it is a good practice to setup the backup interval and copy/restore interval of the Logshipping setup same ( Eg. backup trans log every 30 mins , and restore to secondary server every 30 mins) It is not uncommon to setup the log shipping to Restore the Transaction logs only few times a day, so that users won't be kicked out of the restoring database.

Drawbacks are:

Doing so, you would not get an exact near Production copy of the database.

Your Transaction log to be restored in the secondary database will take more time across the network since there will be more transactional log files.