It’s probably easier to just use smaller images and more compressed audio and just let construct handle the loading.
Construct’s docs say it loads images layout by layout, and audio is loaded as it’s used.
My guess is what the loader does automatically is load the layouts and events data (which is very small) then loads the image files and maybe audio files, and then when changing layouts the textures are loaded/unloaded from video memory from the images.
Anyways I guess one strategy would be to make all the animations use tiny images and load bigger images yourself from the files folder (which isn’t automatically at all).
Overall it seems tedious to side step construct’s loading to do your own. Maybe do some tests?