A typed-specific sequencer pointer p_sequencer tracking issue

In reply to cgales:

Hi cgales/dave,

I’m not able to understand that How p_sequencer compromise the reputability?
I need help to understand that.

My impression about sequencers are that we never modify the sequencer. At most sometimes we need to get configuration to access which can be access by config db from test.

So I believe m_sequencer + config db always fulfills the requirements.
Is there any specific case where we have to use p_sequencer?