No, there is no magic switch (I wish there were) for switching the values from absolute to incremental.
I was in a similar situation with my Shadow (Bandit type) controller, where the canned cycle amounts are always deemed to be incremental.
Here is the gist of what I learned: first, in order to make the simulation work accurately, you need to fill in those first boxes in the "Set clearances" field with, as you know, absolute values.
Next dialog is the "Select a cycle" dialog where you can pick your machine cycles. Note: there will not be any fields to fill in here if you did not associate some variables in "NC setup" canned cycle with the cycle in question.
So, you need to go to NC setup/Posting Format/add cycle (if you haven't already), then select a particular cycle to work on. Now, you can mess around with the default variables from the list of "Insert and Substitutions" if you like, but I think that absolute values are still the rule there. So, click "Add" to create a new variable. You can rename it to whatever is meaningful, instead of using the default name "parmater No 8" or whatever.
Then, set up your canned cycle using these custom variable names.
You can create as many as you need to fill in each parameter of your drill cycle. These new variables will be "stand alone" and they will show up in the NC canned cycle wizard in the "Select a cycle field". These values that you insert now, will be retained exactly as entered, and will be used to fill in your cycle values.
Take note: altering your canned cycle setup will cause problems when opening older files made with the canned cycle set up in a different fashion. One method to avoid this, is to create this new cycle setup under a new and unique Post name, leaving your old post as is.
This gets cumbersome to keep track of, so I simply "bite the bullet" and change it anyway. Whenever I open an old file containing drilling cycles, I simply delete all the cycles and do them again. If I still get a crash, then I delete the file in settings called NCGlobal_inch.bin, or if you work in metric, I suppose it would be NCGlobal_mm.bin. This contains your list of variable choices you have used in previous sessions. This is where the corruption occurs if you add new things to your nc cycles, because the new cycle cannot reconcile with the old. This is an active, temporary file, and is harmless to delete. However, you will note that you have to start over with tool and material selections, not a big deal really.
This topic is hashed over quite thoroughly in this thread link below, but if you get stuck with particulars, just ask away here.