No, don’t do that. The person/s who review your PR have to be the person/s working on that codebase. I would need to understand the codebase (this is a massive thing you are asking, as I keep trying to get across to you), install the extension, run it to figure out how it works, fetch your fork of it, run that, etc. I’ll be blunt here: I’m not prepared to do that. It’s what I do for a job, and it takes large amounts of time, and as I am employed to do my job, I can’t do another job at the same time.
If you do not understand how to work with this specific part of the codebase’s internal API, and you want help here, you need to provide a small, concrete, reproducible example of the thing you’re stuck on. If it’s more general and you cannot do that (which seems to be the case here), you need to ask someone working in the codebase to explain it to you in terms you understand.
This is not a tiny thing like an FCC algorithm problem (for example). You can’t just say “I’m completely stuck and don’t know how to approach this” and just expect useful help here (rather than asking people who actually work on the code), because it’s a large, complex real-world codebase. I don’t think you quite understand the magnitude of what you’re asking of people
It is likely that this is quite a simple thing: the issue has been tagged by the maintainers as good for beginners, so I can’t see why they would have done that if it was super complicated. But you need to ask one of them to get past this blocker.