See the Limitations of Flash Memory.
Read Disturb
The method used to read NAND flash memory can cause nearby cells in
the same memory block to change over time (become programmed). This is
known as read disturb. The threshold number of reads is generally in
the hundreds of thousands of reads between intervening erase
operations. If reading continually from one cell, that cell will not
fail but rather one of the surrounding cells on a subsequent read.
But:
To avoid the read disturb problem the flash controller will typically
count the total number of reads to a block since the last erase. When
the count exceeds a target limit, the affected block is copied over to
a new block, erased, then released to the block pool. The original
block is as good as new after the erase. If the flash controller does
not intervene in time, however, a read disturb error will occur with
possible data loss if the errors are too numerous to correct with an
error-correcting code.
Since the threshold is in the hundreds and thousands of reads, the effect of only reading the flash drive would be minimal; it is more probable that it'd die due to physical harm, rather than because of wearing out.
You should also be aware that there is a lifetime issue with data stored on a flash drive. Data is stored as a series of static charges - over time those charges will dissipate and your data will evaporate, though again, a reasonable expectation for you to run into that problem would be about 10 years.
In conclusion, you can safely assume that your method won't affect the lifespan of your flash drive to the extent that it will be the major cause of your flash drive's eventual death.
More info here and here.
Just to be sure: By usb, do you mean a USB-Stick with SSD? – Marcel – 2014-11-03T08:35:45.027
This might be of interest to you: http://boards.straightdope.com/sdmb/showpost.php?s=389ce49d533810fc916db2d18ebe73b6&p=16229274&postcount=5
– Marcel – 2014-11-03T08:39:50.137No SSD, just plain usb 2.0 stick – user128712 – 2014-11-03T08:46:39.040