1) first of all -- it is not that blocks 2, 3, 4, and 5 are free -- it is that extents 2, 3, 4, and 5 (each having 100 blocks) are unused but (in this case) UNUSABLE since extent #1 is still active.  We use rollback segments in a circular buffer.  We use extent 1, 2, 3, 4, 5, 1, 2, 3, 4, 5, ..... over and over.  If we are in extent five and need more space, we will try to use extent #1.  If that is still active -- we must extend the rollback segment itself.  I can demonstrate this fairly easily.  In one session I execute:
ops$tkyte@ORA717DEV.US.ORACLE.COM> create rollback segment rbs_demo
  2  tablespace dict_managed
  3  storage ( initial 1k next 1k maxextents 50 minextents 5 )
  4  /
Rollback segment created.
ops$tkyte@ORA717DEV.US.ORACLE.COM> 
ops$tkyte@ORA717DEV.US.ORACLE.COM> alter rollback segment rbs_demo online
  2  /
Rollback segment altered.
ops$tkyte@ORA717DEV.US.ORACLE.COM> 
ops$tkyte@ORA717DEV.US.ORACLE.COM> drop table t;
Table dropped.
ops$tkyte@ORA717DEV.US.ORACLE.COM> create table t ( x int );
Table created.
ops$tkyte@ORA717DEV.US.ORACLE.COM> set transaction use rollback segment rbs_demo;
Transaction set.
ops$tkyte@ORA717DEV.US.ORACLE.COM> insert into t values (1);
1 row created.
Now, leave that session open -- we are using a teeny tiny bit of the first extent in rbs_demo with our insert (we are using 1 block).  Now, open another session and execute:
ops$tkyte@ORA717DEV.US.ORACLE.COM> insert into t select object_id from all_objects where rownum <= 1000;
16990 rows created.
ops$tkyte@ORA717DEV.US.ORACLE.COM> commit;
Commit complete.
ops$tkyte@ORA717DEV.US.ORACLE.COM> 
ops$tkyte@ORA717DEV.US.ORACLE.COM> begin
  2    loop
  3         execute immediate 'set transaction use rollback segment rbs_demo';
  4         update t set x = x+1;
  5         commit;
  6         dbms_output.put_line( 'updated....' );
  7    end loop;
  8  end;
  9  /updated....
updated....
updated....
updated....
updated....
updated....
updated....
updated....
updated....
updated....
updated....
updated....
updated....
updated....
updated....
begin
*
ERROR at line 1:
ORA-01562: failed to extend rollback segment number 7
ORA-01628: max # extents (50) reached for rollback segment RBS_DEMO
ORA-06512: at line 4
ops$tkyte@ORA717DEV.US.ORACLE.COM> select used_ublk from v$transaction;
 USED_UBLK
----------
         1
See, we are using 1 block of RBS data -- we did a couple of updates successfully (so we know our update takes LESS then 50 extents of data to accomplish) yet we eventually ran out of rbs since we had that one block used in extent 1 -- we added 45 extents and eventually ran out of extents to add.  All because of that sole uncommitted transaction.
2) I cannot imagine any circumstance under which the "feedback option" would not appear unless you were perhaps on a slow network and the last bit of the page didn't come over (or you hit stop or something).  Its always there.  I never turn that off.