Well sure, there are potential solutions, and I mentioned some of them in my earlier posts (Modify the PHP settings, Copy'n'paste in smaller chunks, use different software).
You could also build content pages offline (using your computer's resources), put them up with ftp, and them include them in your Drupal/Joomla!/whatever via PHP include statements or ssi.
I'm not in favor of extending execution time of PHP scripts to 60 seconds on a shared webserver - a webserver's job is to serve pages, not conduct general purpose data processing.
I believe people should be respectful of RAM and CPU resources on a shared server so that all can use the machine productively.
I'm sorry, but I don't see this as a major issue at all. There are so many alternate ways to "scrape" another site's content other than a "cut'n'paste" of huge chunks of others' work via an "online editing environment" in a CMS (if you want to do such a thing).
Besides, the web is all about links - if you want that much of the content from another site, just link to it (or mirror it, if allowed); "republishing" it verbatim is just pointless, IMHO.
That said, if you want to do it there are plenty of "solutions for this problem" - including a DreamHost PS server where you can reserve machine resources for you own use, or a dedicated server where you can let processes run as long as you like.
You can also doink around with your php.ini settings to extend some of those limitations until you reach the point where the proc killer kicks in - and then live with the results, or find another way to do it.
I understand that the proc killer may be frustrating at times, but it is entirely necessary for a shared server where many users are not conscience of, respectful or, or knowledgeable about the use of machine resources. Without it standing watch, any idiot on your server could monopolize it's processing abilities, and/or overload it, to the point where neither you nor anyone else on your server could load a page. This is part of being on a shared server; if it is too restrictive for your needs, then a vserver or a dedicated server is probably best for you.