@jmbattis for the three variable arguments you should be able to choose any output variable that is associated with either a thermal zone or a building surface. Zone consumption or peak load per reporting frequency should be fine.
As far as changing the frequency you would have alter the code below to add in additional frequency options, but keep in mind the measure hasn't been tested with other values.
chs = OpenStudio::StringVector.new
chs << 'Timestep'
chs << 'Hourly'
reporting_frequency = OpenStudio::Ruleset::OSArgument::makeChoiceArgument('reporting_frequency', chs, true)
reporting_frequency.setDisplayName('Reporting Frequency')
reporting_frequency.setDefaultValue('Hourly')
args << reporting_frequency
I would specifically be careful with detailed, as it may be variable time step and measure may not be setup to handle that. I don't see any reason daily monthly or run period won't work, but would impact behavior of animation that steps through time and days.