It is only a graphical representation of the concept. Both are identical in execution.
Create a table that needs two relationships to the same table.
Create the first relationship. Fine
Create the second relationship. You are prompted. "A relationship already exists, Do you want to edit the existing relationship? To create a new relationship, click No" The question is badly worded so you have to say No to create the new relationship. Access then creates a suffixed table. If you delete the suffixed table (this does not alter the relationship). No prompt happens. Close the Relationships window and then reopen. The suffixed version reappears. It is quite possible that this behavior varies with versions but this is how mine is working "today"
You can always see the actual relationships by opening the MSysRelationships table.
Can one do this as a way to create less of a spider web in the relationships window?
There are instances where the Relationship window "forgets" all your hard work laying out the graphic design. When Access rebuilds the graphic, I think it builds it in the order the relationships were created but that is just a guess. In any case, it is almost always a mess. SQL Server has a better graphic tool. It allows you to segment parts of the schema to minimize noise and multiple pages of crossing lines.
However, If you put your mind to it, you can remove most of the noise by changing the placement of the tables to make the relationships more logical. Usually, it is only my state table that causes the crisscross lines but sometimes I have other lookup tables that are used in multiple places such as Prefix and Suffix for names.
I don't see any correlation between the spider webby appearance and the proper designation of relationships.
There isn't any but a messy diagram makes the schema much more difficult to comprehend. If you have a schema that takes more then two pages to print, it becomes next to impossible to keep the picture organized. I've been known to upsize the tables to SQL Server simply to be able to produce a better diagram. There are other tools but I don't own any of them these days. I've forgotten the name of my favorite but it was very expensive. Several thousand dollars per seat.
I print out the diagrams, and hang them on the wall for reference.
I also save a copy of the diagram report so that if Access "helps" me and scrambles my diagram, I don't have to think about it, I have a copy that shows me how to fix it again.