If you don't mind to add as many extra fields as you have recordtypes for your custum object, then here is a little workaround:
Create the extra (text) fields in your custom objects, like:
Field_for_RT1 and Field_for_RT2

Create a trigger for your (custom) object something like this

trigger CustomObjectName on CustomObjectName__c (before insert) //Replace CustomObjectName by the real name of your object
{  Id RT1 = Schema.SObjectType.CustomObjectName__c.getRecordTypeInfosByDeveloperName().get('RecordtypeName1').getRecordTypeId(); //replace RecordtypeName1 by the real name of your recordtype
    Id RT2 = Schema.SObjectType.CustomObjectName__c.getRecordTypeInfosByDeveloperName().get('RecordtypeName2').getRecordTypeId(); //replace RecordtypeName1 by the real name of your recordtype
  for(CustomObjectName__c COName : Trigger.new)
 {
     COName.Field_for_RT1__c = RT1;  //here you store the ID of recordtype 1
     COName.Field_for_RT2__c = RT2;  //here you store the ID of recordtype 2
}
}
If you deploy this to a sandbox or production, you don't need to change anything because it get's the RecordType of the sandbox of production
Now you can use the this field as field reference or in a formula where you pick the Field_for_RT.. you need.
Of course you can also use a trigger to change the recordtype when all the required conditions are met. In that case you get the id as mentioned above and in the for section you change it by: COName.RecordTypeID = RT1 (or RT2) and you don't have to make the extra fields