I would not make sense (in my opinion) for us to automatically reset the sequence numbers because it could lead to clashes with existing "used" values.
All that the scale attribute is doing is controlling the ranges that are built - but it is still just a "normal" sequence, so if you 'noscale' it, then we continue on from where we left off.
Once noscaled, you can reset it using the negative increment method as we've always had, eg
SQL> drop sequence s;
Sequence dropped.
SQL>
SQL> create sequence s scale;
Sequence created.
SQL>
SQL> select s.nextval x from dual;
X
---------------------------------
1010790000000000000000000001
1 row selected.
SQL>
SQL> alter sequence s noscale;
Sequence altered.
SQL>
SQL> select scale_flag from user_sequences where sequence_name ='S';
S
-
N
1 row selected.
SQL>
SQL> select s.nextval x from dual;
X
---------------------------------
1999990000000000000000000002
1 row selected.
SQL>
SQL> alter sequence s increment by -999990000000000000000000000;
Sequence altered.
SQL>
SQL> select s.nextval x from dual;
X
---------------------------------
1000000000000000000000000002
1 row selected.
SQL>
SQL> alter sequence s increment by -1000000000000000000000000000;
Sequence altered.
SQL>
SQL> select s.nextval x from dual;
X
---------------------------------
3
1 row selected.
SQL>
SQL> alter sequence s increment by 1;
Sequence altered.
SQL>
SQL>
SQL> select s.nextval x from dual;
X
---------------------------------
4
1 row selected.
SQL> select s.nextval x from dual;
X
---------------------------------
5
1 row selected.
SQL>