No, I'm not saying that.

I'm saying that the recovery process after a restore (log, full or diff) reads the log backup from the backup file. It's not first written into the transaction log and then recovered from there. Now I don't know offhand how the backed up log is architected, whether it has the same VLF structure as the log itself or not. If it doesn't, if the log backup is a single chunk of log records, then recovering after a restore won't be subject to the same overhead of opening every single VLF in the transaction log file.

That said, every article, post, discussion which talks about the impact from lots of VLFs, talks about the impact on operations which read from the transaction log (backups, crash recovery, etc), not restore operations.