OK, I believe there are great opportunities to optimize aMule on the mac. Running isulzers compile from March 26th, I had aMule hog as much CPU as it could get running just one download at 100-200K and 70 sources. The upload was only 50K. This 1.5 GB file, together with two small files, where the only ones shared.
Now, I refuse to believe that this should tax my 1.33 GHz G4, granted it is not the best CPU, but I've run eMule on a 733 MHz P3 back in the day, and it used only a couple percent of the CPU. Also, I remember commercials from Apple, where the G4 spanked the P3

Now, I'm no programmer, so I won't be able to help at all, except coming up with information. I don't know what dev utilities you have on other platforms, but Instruments is a great app from Apple that let you sample processes and visualize the information. I'll attach a sample from when I experienced this CPU usage (this was actually done with sample from the CLI).
Let me know what else can be helpful, and I'll do my best to get the information you need.
Oh, and it would be nice if someone else with a mac could confirm that they see the same problem, so it's not just my system that's slow.