Even if preset records were to be loaded in a fixed order, IDs are unreliable, because when you update an application and add new presets, other records might have been created in the meantime.
You can use a unique name attribute (preset attribute value should then be protected!) to look up record IDs, but there is a much better way. In both front- & backend functions, you can use the instance function call
get_preset_record_id(). This call needs the preset ID (which you can find next to the preset in the Builder) and returns the valid record ID in the current system. This way you always get the correct record ID wherever you need it.