@derBoogie Same issue here. Did you find a solution yet?

My szenario:
2 plugins on the same page with different storagePids set in each plugin.

I tried to analyze the bug with Xdebug. When I put a breakpoint in PostRepository.php to public function initializeObject() and protected function getPidsForConstraints() Xdebug stops at initializeObject() only once while getPidsForConstraints() is called twice.

An Extbase repository is a singleton, i.e. only one object of that class exists.
EXT:blog reads the settings into a class variable in initializeObject(). However, the settings are dependent on the context when they are read, i.e. they can be dependent on the content element.
The second content element uses the repository again - only it already exists as an object, which is why it can be used immediately and is not initialized (i.e. the settings are not read in again).

Based on v11, it seems to work if you change getStoragePidsFromTypoScript() back to:

protected function getStoragePidsFromTypoScript(): array
{
    $configurationManager = GeneralUtility::makeInstance(ConfigurationManagerInterface::class);
    $settings = $configurationManager->getConfiguration(ConfigurationManagerInterface::CONFIGURATION_TYPE_FRAMEWORK);

    return GeneralUtility::intExplode(',', $settings['persistence']['storagePid']);
}

@peterkraume thanks for your debugging.
@julianhofmann thanks for your analysis. Your solution works!