Customize FixtureMappingManager / fixture instantiation without overriding the full test pipeline #3567

Hello !
I'm currently working on an integration test framework based on xunit
(i made a post earlier).

In this integration test framework, i enabled the possibility to use dependency injection.

My fixture is what i called an environment, and an environment is a collection of infrastructure.
For now, Environment (the fixture) initialize an a service container, and instanciate every infrastructure with it.
Enabling DI inside infrastructure.

Environment needed dependencies too, so for know i've been using the ServiceProvider as a service locator directly in the environment.
But, i would like to pull the DI up, so environment (fixtures) could be instanciated with a ServiceProvider.

I found that XUnit.DependencyInjection does that, but not really how i want.

Here is my goal:
have a custom FixtureMappingManager (specifically GetFixture), that do a ActivatorUtilities.CreateInstance() with a service provider in addition of the current behaviour.

// FixtureMappingManager.cs L170
// Create the object
try
{
	// result = ctor.Invoke(ctorArgs); -- not anymore
	result = ActivatorUtilities.CreateInstance(serviceProvider, fixtureType, ctorArgs);
	// Service provider would be provided by finding the nearest DI configurator from the test class.
	fixtureCache[fixtureType] = result;
}
catch (Exception ex)
{
	throw new TestPipelineException(string.Format(CultureInfo.CurrentCulture, "{0} fixture type '{1}' threw in its constructor", fixtureCategory, fixtureType.SafeName()), ex.Unwrap());
}

Is there any known way to customize this without overriding the whole test pipelines ?
(TestFramework, Executor, Assembly, Collection, Class runners, etc...)

I hope i didn't missed something on the doc/code that could answer that question.
Thanks for the help anyway!