I think this question, similar to the one you refer too are both very broad scoped and does not ask a specific and clear question.
Rather than find something to analyze the behavior of existing software, why not instead go to GitHUB and grab the PulseAudio source code, and start reading it to better understand how it works. There may also be documentation for the code, I haven't checked. Then experiment by adding some debug, changing some of the source, to learn more about it and to help you with a better understanding of the way this code works.
Also review the
PulseAudio Wiki, if you haven't already, and see about contacting the developers with some deeper questions about the structure of this code.
While you review and experiment with the source, you may have further questions, and you certainly can post them to LQ. I suspect though that unless there are LQ members who know the PulseAudio source very well, the answers may be limited to the scope of code you can post for opinions or thoughts and the amount of visibility members here can gain into that source while not expending time beyond their personal thresholds to try to help you. This is why I feel that some of the questions about this source may be best posed to the current maintainers of the PulseAudio source.
For starters, have you downloaded the PulseAudio source from
here, or
here, reviewed their guide on how to build and install it
here, and then tried to build it, install it, or review the code?