Veeeery interesting!

The way I see it, a Bar should just be a place-holder, like a mount-point in Linux, or a cup, which we can fill with whatever we want.

If you want to put a single tick on a bar, then line-chart it and zoom in or out to check out the waves, then go for it. Want a dozen ticks per bar, or a thousand? Easy enough.
Bar = Ticks(However_Many_You_Want);

Prefer seconds, minutes, hours, etc?
Bar = Time_Unit(However_Many_You_Want); // The most artificial bar that was ever invented! Also, the most deceptive!

Range bars or Renko?
Bar = RangeBar(Whatever_Range_You_Want);
Bar = Renko(Whatever_Number_Of_Pips_In_One_Direction_You_Want);

The bugger is that it will increase training/testing times when you first use them, as they will have to be built on the fly... If they're saved after the first test, though, it becomes quicker to add fresh data to them.

Ticks tell us everything we need to know, (unless you're getting them from crapt4), and analysing the information they hold is much easier if you leave the tocks in the clocks.

Anyways, that's my 2 shoes' worth.