Certainly not advised, but you could manually edit the timeout in the DB if you look at Dbo.DiscoveryProfiles and the column -[JobTimeout]
With such large discovery ranges, you increase the risk of causing Out-Of-Memory errors running the jobs. It would really be best to split them up.