If you're running a straight Perl application (not embedded within Apache/mod_perl), the only other thing I can think of is
Devel::SmallProf. Although it is much more granular than
Devel::DProf, if you claim it's not jumping processes than I would imagine the same fault would be in
Devel::SmallProf. Although you may run into the same issue, it's (should be) a one-line change and worth checking out.
This being said, if you are working within Apache/mod_perl, I have had great success with
Devel::DProf and
Apache::SmallProf. Also, if you are running Linux or any other pre-fork worker, I can all but guarentee the profiler will attach to each post-forked child in order to profile them individually.
Other than that I think you may be out of luck... next to modifying DProf on your own :)
---hA||ta----
print$_ for(map{chr($_)}split(/\s+/,join(/\B?:\w+[^\s+]/,<DATA>)));
__DATA__
67 111 100 101 32 80 101 114 108