I created my own code coverage and timing tool, because I have code branches for old Matlab releases and for GNU Octave. It is fairly slow and imprecise, which is why I wouldn't call it a profiling tool.
You could consider doing something like that yourself. One idea would be to have a function with a persistent variable log the time spent on specific lines (either with tic and toc, or with clock). Just before the worker shuts down you write this log to file. Have a each worker generate a unique file name to avoid file conflicts. You can then tabulate the results.
My tool works a bit like that (it also includes a dbstack call to help me track subfunction calls). I hope someone suggests a better way to do this so I can steal that idea.
