3 open questions about s1500 pn io diagnostic user program

Greetings!

I am currently comissioned to create PN/IO diagnostic program for s1500 serie CPUs.
I have based my work on template / examble work supplied by siemens.
More specificly, on this examble program:  https://support.industry.siemens.com/cs/ww/en/view/98210758

The program I've now created works like a charm, but unlike with s300 diagnostic program ("insert and forget"), s1500 one is much more work to be set up, and i am willing to improve it.

Aka, I am trying to find a solution to create something similar that was available on s300 PNIOdiagnostic, "Insert and forget", without the need to use multible inputs and manual adressing to system constants.

I have consept already created to make this work, however there is few open questions that needs to be solved first to make it work.
I am unable to answer these questions myself due of my limited knowledge on TiaPortal V13 and s1500 CPUs.
Being intern and all tend to do that i suppose :D

1. Is it possible to user program regognice which type of OB the program block is called from?
(normal program cycle, diagnostic error, rack failure, pull or plug module ect...)
there are system function calls to fetch parent instance name and path, however TiaPortal and s1500 CPU allows OB to be given symbolic name of anything (OB numbers are no longer relevant to the actual type of the OB).

2. Is it possible to adress parent OB local variables inside of user program block called by said OB, without the use of inputs on the block?

3. Is there a way to user program to search / fetch one or all system constants by datatype rather than by symbolic name?
Some systems may have more than one IO-system, and system constant names for IO-Systems varies debending which type of IO-System is in question (profinet / profibus) and which CPU you use.
Datatype i am interested in is "HW_IOSYSTEM", which is in essence; an unsigned integer.

Thank you in advance~

Thats what I feared. Alas, while optimization is not often not used, I cannot rely soletly on that as at the moment it is turned on, the OB_NUMBER flags goes haywire.

The HMI interface already present in Diagnose_v20 Is very nice solution already granted, and personally i would have loved to use that. however i was comissioned just to create global datablock handling for 3rd party external program interface to use.

While program works now like a sharm, it isnt as simple to install/combine with the future projects as i would have liked.
I was hoping there was a way to create "drag, drop and forget" - solution.

However, I thank you for your help <3