database design: a table to contain all the identifications related to a user: bad idea?

I was wandering if it's a very bad idea to have a table that contains all the identifications related to an entity.

For example, let's say I have 3 tables, each of which contains data about a user. Should I use an extra column called user_id in profile Y settings table or should I use an additional table called user_index and make use of joins?

[1]USER
I.D
email
password
Salt
created

[2]PROFILE
I.D
full name
bio

[3]ADJUSTMENTS
I.D
max_packets
Delivery day

[4]USER_INDEX
user_id
Profile Id
settings_id

Will this make the consultations slower? Is it worth the extra code? Is it even a pattern? Perhaps EAV(I mean I saw something similar in Magento but I'm not sure if this is exactly the same). Can this provide any performance improvement or just a moment of & # 39; OCD-feel good & # 39 ;?

Currently using MySQL 5.7.26 and I was thinking of using InnoDB as a storage engine. The application will be written in PHP 7.3. OS Ubuntu 19.04.

Thank you!