Here is why you don't do this: File locks. Hold onto your hat for this one.
Sharing a FE means you have to take out a Windows file lock on every file you open (and leave that way). So EVERY TOUCH of the shared file now triggers File Access Arbitration. OK, if you opened it shared, the arbitration will be allowed to go through. But the arbitration involves a quick network exchange that you probably wouldn't notice.
Not so bad for a quick exchange, you say? Multiply it times 15 if every one of your users is online at the time.
But I'm not done. With Windows, arbitration is handled by a bit of software called the Distributed Lock Manager. Why distributed? Because on a network, the file system that "owns" a file is the file system that manages the locks for the file. Let's take the good part of your question first: You have a split FE/BE case.
You absolutely CANNOT do anything about the BE because for it to be useful, you have to share it. But if you pick query and form opening modes that minimize locking, you can minimize the window of exposure to the time that the query/form is actively doing something. Optimistic Locks or No Locks will lead to that minimization. The data you transfer from the BE to your local system is necessary because work can only be done in your local system's memory (which is where the Workspace is). Therefore you have to accept that sharing and the network load it represents as a necessary overhead. Some IT network wonks would say "necessary evil."
Before I leave the BE for the moment, you have to understand that Access manages its own APPLICATION-LEVEL locks in the lock file that resides in the same folder as the BE file. These are the .LDB files that record your actions in the database that you opened. So every time you touched the .MDB or .ACCDB file, went through arbitration, or other security-related things, you ALSO did arbitration and mucking about in the .LDB file. Again, for the BE's lock file, you've got little or no choice.
But what about the FE? There, you have the forms and code segments that you must open and bring down to the memory on your local system. I'm not talking about the form's .Recordsource, but the form itself, which is a data structure from the AllForms collection inside the FE file. IT gets locked via the FE's .LDB file which is in the same folder as the FE itself.
When you have multiple users hitting the form, you are making Access work with the lock file from the FE file as well as the locks for the BE file, over and above what Windows requires. So now you have a network exchange to diddle around in the lock file BEFORE you get to diddle around in the FE file itself.
As if that wasn't bad enough, Windows File Arbitration for that lock file WILL involved as well. So you have all that stuff going on behind the scenes over your network. If you don't have at least 100 MB Ethernet, your network will slow to a crawl.
BUT if everyone has their own copy of the FE, let's look at locking a second time.
The BE issue is what it is. No change. Nothing can change that as long as you stay with a shared Access BE file.
However, the FE is now LOCAL to your workstation, which means that your LOCAL file system arbitrates access to that local file. And since everyone has their own copy, it doesn't MATTER whether you opened the FE exclusive or shared - nobody else will be working on it because everyone else has their own local copy, too. No network involved. Arbitration is at MEMORY speed (a few hundred nanoseconds), not NETWORK speed (several milliseconds), for all FE interactions. Even for the FE lock file, THAT is local and operates at DISK speeds (tens of microseconds), not NETWORK speeds.
Since everything in a local copy of the FE is private, you cannot see a collision with another user. Can't happen unless your company is riddled with hackers. You can't trip over someone else who is opening the same form that you are - because it is a different COPY of the same form. With Optimistic or No Locks, even the commonality of that form's .Recordsource pointing to the same BE table or query won't make a difference; just don't use Pessimistic Locking. For Optimistic or No Locks, the touch to the BE is VERY fast and quickly finished. So you have good odds of avoiding usage conflicts. (Which, by the way, is the primary source of database FE corruption.)
TheDBGuy is correct to point out that if you attempted to use FE-based tables as temporary locations, the shared FE is going down like the Titanic because of usage conflicts there, too. We don't always know the mechanism, but remember that you are drawing from the same exact disk blocks for those putative shared FE files AND unlike a quick table touch, the Form or Report WILL be open for seconds or minutes. A VERY wide window of opportunity for usage collisions.