I found an internal problem with a similar case, but found one that matches this scenario. Of course, itโs worth adding a portal to quality. Having said that, I fear that bitmap-based operations and scaling do not work well together, and it can be difficult to have an all-encompassing solution.
Let me explain an example. Take the button. It is colored by FMX with 9 sections (borders, corners, central part), so that regardless of the size of the raster elements, it stretches in one direction to a maximum, often just draw. Stretching a single bitmap for a button with the target size will disrupt the smoothing and create a blurry image when using colors.
This is an example of what happens with ScaledLayout, given that it takes the full final image and converts it. ScaledLayout was originally introduced with vector styles, and worked very well in this scenario. With today's raster styles, things get a little more complicated.
Regardless of this explanation, there is a problem, I would recommend reporting it to QC, and I will make sure that it does not close as a design (this, of course, can happen, this is how the system works), but that we conduct some investigation, to solve this problem by turning it into a function request.