What do you need ?

In service studio when we have entity which refers system entity such Users by default if the System->user Dependency is not added; outsystem will set delete rule to ignore. 
But the issue upon changing changing the delete rule from Ignore to protect , service studio will allow you do so but on the backend this will not be truly a foreign key as the System->user Dependency is not present in the module. Also checking ossys_entity_attr it will also state but the column is set to protect but no referential integrity rule (FK)  was created.

My need somewhat basic and already exists in service studio , a warning message stating to add it as a dependency in order to proceed when adding a referenced value which is a system entity from ignore to protect.

This behavior already exists but for user created entities. 

For system entities no warning message (No feedback and is very open-ended). 

Please note the dependency is not present in module. 

In turn the developer will assume a foreign key is created on backend , but actually isn't.

What could it improve?
This could help Junior developers from making trivial mistake such as 

I.e
Creating an empty module , then creating new entities with using a system entity such as user id and so on. 
Not adding System->user Dependency then changing user created column which references the user table to protect.