I added the other cases (SHA_init, SHA_finish, SHA_update) and parameter checking to TRAP_Sha. Intermediate results do not match yet, but results after SHA_finish match (patent says, intermediate results are undefined but "can be used to store data"). Apart from intermediate results, TRAP_Sha is fine for every call.
My guess for trap 0x320 is TRAP_MemSearch, will look into that soon.
Edit: Here's a new version (including parameter checks for all traps, feel free to bugfix or edit it yourself
):
debugger:
http://uploaded.to/?id=jtslin, logs:
http://uploaded.to/?id=ave7c7
Traps 0x120 and 0x530 seem to be most important to me now (since they require player-data to be emulated). The fixing of the problems with other traps (0x320, 0x140, 0x4*0, 0x520) just takes some more time to implement.