IntSlider again

I don't know if this is a real bug, maybe it's the same thing that causes this.

I needed to replace my Slider with an IntSlider since it controls multiple things, among which a repeat (hence the replace).
I fed the IntSlider to an Assemble RGB (and HLS) to compute the same (reversed) values I got from the previous remapped Slider.
Then I got something weird. I was unable to get white unless I set the IntSliders max value to ten (which is too few steps to my taste).
Also very curious is even though I had first set the max value to 255, the final value would not go higher than 20 (see image). If I then just copy pasted the IntSlider the final value would suddenly display the correct 255 value.
Ps: the remapping of the IntSlider onto the RGB and HLS Assembles is the default 0-255 and 0-100 respectively. It's just to show the weird final values.

Besides this point: when remapping the IntSlider, why is the Assemble get a min-max remap, and a repeat in a profile gradient get a step remap. I'd rather have the remapping of Sliders and IntSliders work similarly so it wouldn't be so hard to get 'the same' results for both Sliders. I know it's probably because we don't want a remapped IntSlider to produce floating points, but it's irritating nonetheless.