As nobody else has responded, here is my take on this.
These sort of things have a good chance to get included if the patch
is simple. If, as you say, the patch is intrusive, then you will have
harder time to get a reviewer & committer for you patch. If it makes
the admin code more complicated, you will also need to show why this
feature warrants the added complexity.
It is not entirely clear to me why admin should support dynamic forms.
So, first things first: can you give some use cases where this would
be useful, and where you can't use the current admin hooks to
accomplish the use case.
The worst thing that can happen is that you create a big patch, but it
turns out the approach is unworkable. So, second step would be to make
a plan of what needs changing and why. Or you can just write the patch
and see what happens. That risks wasting some effort if you took the
wrong approach. But on the other hand that is pretty effective way to
learn the code base... And in some cases writing the patch directly
needs about the same amount of work as writing the plan.
Unfortunately I do not know the admin & forms parts of the code well
enough to give any advice on the correct approach.
- Anssi