Retaining the Multiprocessing folder: pros vs. con?

A recent item in the iBook/AirPort MacFixIt Report noted the importance of retaining the Multiprocessing extension(s) in your iBook's System Folder.

Jeffrey Gayton confirms the same advice for his G4 Mac with a 17 inch Studio Display. Unless the Multiprocessing folder was in the Extensions folder, the G4/monitor had a wake-from-sleep problem.

However, Scott Lahteine found that deleting the "Multiprocessing API Library v2.0" and "Apple CPU Plugins v2.2" files in the Multiprocessing folder of his G4/450 Sawtooth Mac eliminated a problem he had with progressive slowdowns of animation effects invarious applications: "If I interacted with the program (pressing a key, clicking in a window, etc.) the animation would return to speedy, but then gradually slow down again. If I removed the Multiprocessing folder and rebooted, there were no more mysterious slowdowns."

Update: Huck Caton discarded the Multiprocessing folder from his iBook's System Folder and has yet to have a problem.

Kevin Parichan (and others) remind us that the Multiprocessing API is "for threads and can be used for similar kinds of programming tasks as the Thread Manager." It is not restricted to, nor even primarily for, multiprocessor Macs. It is separate from the Multiprocessor API, which is for multiprocessor Macs.