35 minutes? That's child's play. I used to queue up 2-3 songs in the morning on Limewire Napster and hope they'd be finished downloading by the time I got home from work. Half the time there was still a couple hours left for the last song.
When I first used Napster I installed it on the school computer and used the audio out to record it on my Minidisc player. It was quite fast at the time, got like two or three songs per lesson
Probably about 9 minutes for an average song over a 56 kbps connection, without disconnects or hangs. Unfortunately it rarely stayed connected without hangs and stutters, so it ended up taking a lot longer than the math suggests it should. I didn't have a good computer though, nor good Internet. I was using some bargain basement eMachines computer. It wasn't until a few years later that I built my first PC. If you didn't disable automatic updates on Windows or other programs, then those downloads could end up hogging 90% of your bandwidth for the entire time you were away.
How shit does the computer have to be where the machine's performance itself is a factor in p2p torrenting? Like, if it can run Limewire, it should be fast enough where the only relevant bottleneck is the pipe to the internet.
Internet speed and reliability of both host and client are a factor though; downloading something rare where there's only like one guy in Burundi seeding it could take centuries.
Softmodems were painfully CPU intensive vs a hardware/controller-based modems. A slow Celeron proc, as found in most eMachines of the time, was already chugging to keep 98/Me going with everything else.