There's nothing wrong or immature. Just because Windows doesn't tell you about the performance impact and drawbacks of fractional scaling doesn't mean that it doesn't exist.
To understand this tooltip you must understand how pixels are arranged in a display.
If you have a 1920x1080 (1080p) display, that means there is a grid of 2,073,600 pixels arranged in 1920 columns and 1080 rows.
When you use fractional scaling, you are changing how items on the screen are rendered in this grid.
With 200% scaling, the computation to render these pixels is very easy. All you need to do to render 200% scaling is to render every single pixel as a square of 4 identical pixels.
A grid of 4 pixels at 100% scaling (normal):
x y
Y X
Is rendered as 16 pixels in 200% scaling:
x x y y
x x y y
Y Y X X
Y Y X X
The pixels can be scaled in a way where pixels can be duplicated perfectly without division. The image will retain its sharpness because the pixels can be perfectly duplicated.
If you use 125% scaling, this simple multiplication is not possible. In order to render the image, pixels would need to be divided into parts that are smaller than a single pixel. But pixels can't be divided this way, so there is additional computation required to artificially create a pixel mapping at 125%.
This not only requires additional computation, but since those pixels cannot be multiplied without remainders, it can cause the image to appear blurry when compared to 200% scaling or no scaling.