That is a complicated question -
In theory - the answer is broadly 'yes - that is part of what SE LInux is designed to abate'. SE Linux is like driving with handcuffs on, many turns you want to make will not be available, because you can't turn the wheel that sharply. Many third party applications/scripts just won't run without 'turning down' SE Linux ('permissive'/reporting only mode). In fact if you explore the /opt/lampp/lampp bash script that powers LAMPP, you will find an SE Linux hack for Fedora (which comes with SE Linux 'on'). I have several frameworks and tools that will not work with SE Linux because they have working directories where they 'shouldn't be' i.e. under the Document Root (which should not contain 'working data'). Yes, I "could" fix that -- too much work, for little benefit on my development platform, and I know I won't find SE Linux where the code I am building is going.
You won't find SE Linux except on 'owned'/dedicated or VPS servers or Desktops as it breaks too many things, and the average user/admin will never get the fix right. Its much like 'Group Policies' in a Windows environment (although the Windows model is broader, as Windows does not have as many native User Contols) - SE Linux is aimed at applications http://selinuxproject.org/page/FAQhttp://www.crypt.gen.nz/selinux/disable_selinux.html
SE Linux is rarely fully implemented except in highly structured environments, as it is a huge investment in intellectual capital/time to execute properly. So governments, and large organizations are where you typically find SE Linux rollouts. These are also the only places you find many 'working environment' Linux desktops. Its 'a whole enchilada'.