Compiler generated function to copy a structure onto the stack (PUSH for an object) interfers with later analysis

[Wall-AF]

Hi Folks

I'm looking for some help with understanding the function I've included here and how to get Ghidra to utilise it correctly.

It is mainly called just prior to making another function call of a (in)directly recursive nature which, together with the assembly, is suggesting some kind of stack reusing, thus avoiding the dreaded stack overflow issue!

Any help greatly appreciated. Thanks.

[Wall-AF]

Functions where these calls initiate are littered with variables named in_stack_0000ffXX even after additional calls to Analyze Stack!

[Wall-AF]

Lightbulb moment! I've realised this routine is just creating additional stack space and copying the given data into that new stack area (like a compiler added PUSH statement but for an object)! I.e. the equivalent of the call below:
IncStackSpaceAndCopyObj(obj, sizeof(obj));
I think, should be (if the assembly would allow)
PUSH obj

So, question: How do I tell Ghidra this so that it is treated correctly (i.e. so that subsequent function calls recognise the additional stacked parameter/obj)??? Would Ghidra need enhancing, or is there some way to do this now?

[Wall-AF]

Tried inlineing the function to no avail!