You didn't say what context you passed to libunwind, but if you gave it a client context, you would naturally expect a client callstack and not an app callstack, right? Xref feature request issues on providing a callstack library:
https://github.com/DynamoRIO/dynamorio/issues/2414,
https://github.com/DynamoRIO/drmemory/issues/823. For unix, if the private copy of libunwind will operate nicely in an isolated way, maybe the simplest thing is to add support to construct the machine context of the app in the format libunwind wants, if all that's needed is the callstack walk and not callstack storage or persistence or compression. If someone does build that support, please consider contributing it as a new extension library or something.