I don't think it's outputting the filenames into a file that's costly; it's potentially the numerous invocations of findstr.exe (that spawns a new process each time)
and no, max timeout (120s) is a generic value across all tests, and cannot be changed for a single one...