What are we trying to fix with it this macro? I don't think it's a good practice to use PropertyChanged to launch events when nothing changed, better to create a specific event ("Refresh"/"UserInteracted") for example.

I added this in because it handles a lot of work that I would need to do manually otherwise when binding a TextBox Text property to this property. For example, if a user types invalid input, this will let me set the Value to the previous Value and still fire the event, causing the binding to update, resetting the double in the textbox to the previous value with correct formatting.

I could just manually set the TextBox text in SubmitTextbox instead, but this would require extra work to also format the double -> string conversion to remove trailing zeroes. I noticed you added a utility in one of your recent PRs that lets us remove trailing zeroes very easily from a string. I added a comment to go ahead and remove this work around and use your util function once we re-merge with master and pick up that change.

to be sure to not break this function if the XAML is modified:

if(sender == Value)
{
...
}`

The names of these TextBox should probably be changed to remove some confusions and conflicts, I don't expect this->Value to be a TextBox for example:
proposal: ValueTextBox, MinTextBox, MaxTextBox, StepTextBox

Done!