This is a revision of a previous question that I asked (i.e. Check browser compatibility for RequestAnimationFrame and Vanilla JavaScript .animate() API), with new aspects that I have learnt in Javascript. It is I think better than the previous implementation as it is using switch statement's which will only run if certain conditions are met, which means a performance gain I guess. Can anyone spot any issues with what I have so far? A link to the original Question is posted at the bottom of this one for reference. 
        const LoadScreen = document.getElementById("Temp");
        const LoadRing = document.querySelector(".loader");
        setTimeout(() => {
            LoadScreen.style.display = "none";
            LoadRing.style.display = 'none';
        }, 875);
   let webAnimSupport = (window.Element.prototype.animate !== undefined);
   let rafSupport = (window.requestAnimationFrame !== undefined);
   let cssFallback = false;
   function animeFallBack(){
       switch(rafSupport ? true : false){
           case true:
                console.log('.raf(); Support = true');
                runRAFAnime();
                // .animate Not Supported Fallback to `request animation frame`.
                //   Add Callback or Promises in here which holds RAF Anime Code.
                //   Put the RAF Code in an External File to reduce the size of this one.
                //   When Learnt more move the Animations into there Own WebWorker...
           break;
           case false:
                console.log('.raf(); Support = false');
                let requestAnimationFrame = (
                    window.requestAnimationFrame ||
                    window.mozRequestAnimationFrame ||
                    window.webkitRequestAnimationFrame ||
                    window.msRequestAnimationFrame ||
                    function(callback) {
                        return window.setTimeout(callback, 1000 / 60)
                    }
                );
                // Fallback option or alert enable Js
                //  Wrap this in a Try Catch Block & fallBack to Css Anime.
           break;
           default:    // Default to Css Fallback.
            var AnimeStyle = document.createElement("link");    // Default Classes to be added back in.
                AnimeStyle.setAttribute("rel", "stylesheet");
                AnimeStyle.setAttribute("type", "text/css");
                AnimeStyle.setAttribute("href", "FallBack.css");
                document.getElementsByTagName("head")[7].appendChild(AnimeStyle);
                return false;
       }
   }
   switch(webAnimSupport ? true : false){
       case true:
            console.log('.animate(); Support = true');
            RunAnimeApi();
              // Run .animate() functions as normal via Callbacks or Promises.
       break;             // break; 4 WebAnimSupport = True;
       case false:
            console.log('.animate(); Support = false');
            animeFallBack();
                     // Move onto requestAnimationFrame();
       break;        // break; 4 WebAnimSupport = False;
       default:
          return false;
                     // Default to Css Fallback. ie ``Add Back in the Classes`` That governed the original Animation.
   }
Ideally I would like to include promises within this block but these are something I'm still struggling to wrap my head around. Can anybody spot any mistakes, performance gains or security issues with this current implementation?
Related Articles:
    paul irish polyfill
    .animate polyfill();
    requestAnimationFrame(); polyfill
    Game Loop Crashing my Browser
    requestAnimationFrame polyfill produce a timestamp aswell
    requestAnimationFrame polyfill error in jest tests
    Do we need to clear a timeout when using requestAnimationFrame polyfill
    requestAnimationFrame polyfill argument
Maybe Related:
    Check if two elements exist in an array with older browser support
    mozilla.org/en-US/docs/Web/API/Element/animate
    Waapi better api web animations
Kind of related:
    What is the best polyfill for requestanimationframe out there
    Npm request-animation-frame-polyfill
    Ember Cli requestAnimationFrame Polyfill        
Test Browser Support in Older Broswers:
    browsershots.org
    browserling.com
    sitepoint.com/cross-browser-testing-tools
Will Update soon.