[Galaxy Note 10.1 Q&A, Help & Troubleshooting] esgie:
Have you ever investigated this subject that you are so sure? If you cannot do it - don't assume that no one can.

I don't also see any relation between dimming the screen and protecting the battery of getting broken. If 5% level is a level on which the battery should be charged because of the damage risk, then it would be absurd to dim the screen (ie take an action aimed at saving the remaining power so the user can work a few minutes longer on the last remaining 5% until it reaches 0 or 1% = drain battery even more = in your theory: increasing the risk of the damage even more), and not to turn off the device at all. Be aware, that Samsung indeed implemented a protection aimed to secure the user of the risk of breaking the battery (well, I don't think it's the clue anyway - iI guess the main purpose is in preserving user of data loss/filesystem corruption, which is possible to occur when the system is being shutdown in an "immediate" way, without chance to perform shutdown sequence properly) due to full discharge, but it is triggered on 0 - 1% level and is resulting in starting a "regular" system shutdown, aimed mainly to save all the working data before user loses it *** See comment at the very end of my post for additional info about changing this behavior, which is confirmed to work by myself...

It is almost ALWAYS possible to mod behavior of the system, especially by decompiling system apps and modyfing smali, which is not extremely difficult/impossible by the way, as the community has released such a solutions for many issues/feature requests, concerning even n8000 itself (ink lockscreen, syscope disable, power menu, flashable themes...).

In this case, I can see another possibility, which is even less intrusive to the system; AFAIR the percentage level of 5% is not embedded in some system or framework app, but it is defined in one of the system's apps preferences (guess settings provider? dont remember...), in sqlite database. And sqlite database can be easily accessed and its content can be modified by sqlite tools, ie sqlite3 binary from command line, and even some apps from play store. Then, you shall be able to lower the value to, for example, 1%, so the screen backlight will be turned off with further delay, ie. at REALLY critical power level of 1%..

EDIT: Didn't found above setting, dont have time for this, but found another one (at database lying at com.android.provider.settings) - "dim_screen" which is set 1 by default. Maybe changing it to 0 with any SQL editor will force NOT to dim screen at all.

An for the begin, I have a solution that is very very very possible to work...

As for now, I have not tested it, especially if the critical battery level setting (default 5%) has direct relation to the battery level on which screen is dimmed, but I am ALMOST sure about it, as the crtitical level setting that I am talking about (no matter where it is stored...) is recognized system-wide.

Oh, almost forgot, the solution!!! :)

Install Xposed Framework (search for it on xda if u dunno what it is) + module XBatteryThemer - apart of other options, it has the option to lower critical battery level (as well as two other levels, which determine displaying the low battery alert popup) to as low as 1%. Your screen shall no longer dim at 5%.

*** actually, there is another one Xposed module (CriticalBatteryShutdown, or something...?) which can force the device not to turn off when battery reaches some level between 0 and 1%, which is arbitrary action by default. With this mod the device is working untile theres really no power left, which sometimes can give you additional 10 minutes. A