Table relations & choice as filter

Now that you brought this up, from a design perspective I read (thought I read/thought I understood) that you should not use the ‘user profile’ table except for ‘user’ info from a security perspective.

But the user profile is the one table that is accessible in actions, visibility and filters so it has become a very wide row with lots of USC/xxx columns with many templates/filters plus relations and is the source for four of my five TABs and many ‘New Screens’,

Is this a reasonable/usual best practice? I especially needed access to data within actions which have a very limited scope.

TIA