Their recommendation tries to cover all bases, even though the attack vector is extremely unlikely and requires explicitly misconfiguring your site.
While I plan on making it an option in the next version of Admin Tools I don't think it's something that all (or even the vast majority) of sites need. If you really have a site allowing untrusted users to upload SVGs and you have a scenario where a Super User could be duped into opening a potentially malicious SVG file in their browser while logged in to the site's backend you might want to add that code into your .htaccess. But, seriously, this is not an attack vector I'd lose sleep over. The rule of thumb is: if you don't absolutely trust the source of an SVG file don't open it, don't use it, delete it immediately. Same as with any other executable file.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!